Skip to content

Update the cache settings in Py SDK #28

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

Merged
merged 3 commits into from
Jan 13, 2025

Conversation

Spatika-Ganesh
Copy link
Contributor

Copy link

linear bot commented Jan 11, 2025

WOR-2424 Cache Settings

guillaume I suggest we change our cache settings to: — inspired by Braintrust.

The cache follows the following rules:

There are three caching modes: auto (default), always, never.
In auto mode, completions are cached if they have temperature=0.
In always mode, completions are cached.
In never mode, the cache is never read or written to.

currently, our default WHEN_AVAILABLE will cache completions even when the temperature is not 0 — which is a bit confusing I think. We even had to adjust our own playground logic to account…

What do you think?

For a migration, we can make WHEN_AVAILABLE the same than AUTO


  • API changes
  • SDK changes
  • Code Generation changes

guillaq
guillaq previously approved these changes Jan 13, 2025
@Spatika-Ganesh Spatika-Ganesh merged commit bb7c5a9 into main Jan 13, 2025
5 checks passed
@Spatika-Ganesh Spatika-Ganesh deleted the spatika/cache-usage-literal-update branch January 13, 2025 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants