Lastly, could you describe what part of the documentation based on caching is not up to par? We strive for a fully documented API and feedback is always welcome

At this point I feel the documentation on caching is quite hidden (could only find it in https://typesense.org/docs/29.0/api/server-configuration.html#resource-usage). I’d expect it’s own section somewhere in the vicinity of https://typesense.org/docs/29.0/api/vector-search.html#index-embeddings. Furthermore, I think it should explain in more detail how the caching behaves exactly. Technically speaking, e.g. the question on my mind is: how is the caching key constructed / which input goes in? Does it hash only the document contents or does it also include e.g. the chosen model and any parameters going into the embedding generation? Under which conditions will the embedding be recalculated, when will it be taken from the cache? Is the cache persistent and thereby survives server restarts? Is the cache distributed and therefore works in a clustered scenario? Some one of these questions are going beyond what I need, but these are examples of questions that come to my mind when I read about a caching feature. I could look at the implementation to get answers, but the implementation might just be a snapshot and the behaviour might change without me noticing. Documentation typically serves more as a “specification”, describing how things should work.