Skip to content

fix(judge): honor concurrent_requests for the OpenAI/TGI judge backend - #1371

Open
mohansree14 wants to merge 1 commit into
huggingface:mainfrom
mohansree14:fix/judge-parallel-concurrent-requests
Open

fix(judge): honor concurrent_requests for the OpenAI/TGI judge backend#1371
mohansree14 wants to merge 1 commit into
huggingface:mainfrom
mohansree14:fix/judge-parallel-concurrent-requests

Conversation

@mohansree14

Copy link
Copy Markdown

The litellm judge backend already reads backend_options.concurrent_requests (via LitellmBackendOptions, default 10), but __call_api_parallel — the path used for the openai and tgi backends — hard-coded ThreadPoolExecutor(10) and never looked at backend_options at all.

This reads the same concurrent_requests key there (defaulting to 10 when not set), so concurrency is configurable for every judge backend, not just litellm — closing the remaining gap from #567.

Fixes #567

The litellm judge backend already reads backend_options.concurrent_requests
(LitellmBackendOptions, default 10), but __call_api_parallel -- the path used
for the openai and tgi backends -- hard-coded ThreadPoolExecutor(10) and never
looked at backend_options at all. Read the same key there, defaulting to 10,
so concurrency is configurable for every backend, not just litellm.

Fixes huggingface#567
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.

[FT] LiteLLM concurrency parameters hard-coded

1 participant