huggingface/lighteval

[FT] LiteLLM concurrency parameters hard-coded

Open

#567 opened on Feb 16, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (514 forks)auto 404
featuregood first issuehelp wanted

Repository metrics

Stars
 (2,496 stars)
PR merge metrics
 (PR metrics pending)

Description

I noticed that for LiteLLM the concurrency is hard-coded for an arbitrary number (20). Well, a lot of the request behavior is hard coded, but the concurrency is the one that is probably least likely to work well as a one size fits all.

If everything is going through the YAML file, maybe it can be expanded, although the YAML file is another ball of wax (makes automated runs much harder when you can't just pass in parameters via a call)

Contributor guide

Research direction
Investigate the LiteLLM integration code to identify where concurrency is hard coded (likely in requests or session management). Propose a method to make it configurable via YAML or function parameters.
Tech stack
python
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonLiteLLM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60