Skip to content
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

[backends] Benchmark configuration file to change settings such as openai-compatible API backend #112

Open
Gnurro opened this issue Aug 7, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@Gnurro
Copy link
Collaborator

Gnurro commented Aug 7, 2024

Currently the retry values like number of tries before abort and delay before retrying are part of the openai-compatible API backend code.
However, different providers have different limits, for different models (groq, for example), so it would be good to have the retry behavior set in an external file instead of code that should be kept static between different projects and experiments.
The retry library (https://github.com/invl/retry) allows for more dynamic retryng as well, so a retry configuration could handle different return codes/payloads differently, allowing to dynamically adjust retrying to the provider/API limits/model.

@sherzod-hakimov
Copy link
Contributor

Maybe it makes sense to have a configuration file for each benchmark run that includes info such as

  • max tokens to generate
  • delay time, number of tries

@sherzod-hakimov sherzod-hakimov changed the title [backends] External retry settings for openai-compatible API backend [backends] Benchmark configuration file to change settings such as openai-compatible API backend Aug 7, 2024
@Gnurro
Copy link
Collaborator Author

Gnurro commented Aug 7, 2024

Right, one consolidated configuration file for a specific benchmark run could hold these kinds of settings as well. It might also allow for specifc pre-set combinations of instances and models as I've seen with student projects using clembench - these are currently done as shell scripts, which some potential users might not be familiar with.

@davidschlangen davidschlangen added the enhancement New feature or request label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants