Replies: 2 comments 18 replies
-
Thanks for the suggestion! Current behavior: prompts are refetched (blocking) after the configured cache TTL, they are not fetched on every call Suggested behavior: prompt are refetched after configured cache ttl but stale cache is served. I'd probably rather not have prompts refetch after first use on scheduled interval in background, this has the risk of refetching prompts which are not frequently used What do you think about this @ajram23? |
Beta Was this translation helpful? Give feedback.
-
@marcklingen To be honest, cache seems like a hack when you have versions. Curious why would you refetch prompts which are not frequently used if their versions don't change? May be I am missing something. |
Beta Was this translation helpful? Give feedback.
-
Describe the feature or potential improvement
Prompts don't change in seconds or minutes. And I don't want to fetching the prompt from your server for every call. What would be be better is for the prompts to be cached and provide a mechanism for looking for updates(for newer versions) and updating the cache. And not make this part of the execution pipeline.
Additional information
Submitting as requested by Clemens from Langfuse based on our conversation on Intercom!
Beta Was this translation helpful? Give feedback.
All reactions