-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why use helicone? #12
Comments
AFAIK LiteLLM does not support a managed caching solution, the docs only mention self-managed Redis. |
Tracking this here - BerriAI/litellm#432 Do you want us to provide a hosted caching solution? @nsbradford |
TBH, not a top priority - writing my own cache also only takes <1 hour and then I don't have to worry about whether the 3rd-party caching middleware is reliable, which is why in practice I tend to write my own cache on larger projects |
(would be open to it if implemented, though.) |
SemanticSearch/backend/llm.py
Line 13 in f8189d5
Hey @nsbradford,
I saw you're logging responses to promptlayer but also using helicone. Curious - why?
If it's for caching - is there something in our implementation you think is missing - https://docs.litellm.ai/docs/caching/
The text was updated successfully, but these errors were encountered: