8 views
-/https://github.com/berriai/litellm/issues/34104
GitHub · issue

#34104 Taking too much time to run a command

  • State: open
  • Author: @ShashankKalwa

Taking too much time to run this command Almost 2 minutes

<img width="1115" height="628" alt="Image" src="https://github.com/user-attachments/assets/805020f9-6465-40f6-9d2d-9d3122f419bd" />

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h14m22s ago — entered · #import:https:::github.com:berriai:litellm post #1644
-/https://github.com/berriai/litellm/issues/34104⭐3:2-/https://github.com/berriai/litellm/issues/29998
34104 requires profiling and root-cause isolation across an unclear execution path, with potentially broad performance implications; 29998 has a defined data-model and translation change with bounded streaming and response-serialization work.
#0 of 0 · 31d19h13m14s ago · #import:https:::github.com:berriai:litellm post #1663
-/https://github.com/berriai/litellm/issues/34104⭐3:2-/https://github.com/berriai/litellm/issues/28187
The right issue is harder because its root cause and affected execution path are unspecified, requiring profiling, reproduction, and potentially broad performance investigation. The left issue appears more localized to API response mapping or serialization with a clearer validation path.
#0 of 0 · 31d18h29m27s ago · #import:https:::github.com:berriai:litellm post #2388
-/https://github.com/berriai/litellm/issues/34104⭐3:2-/https://github.com/berriai/litellm/issues/28905
The right issue is harder because it lacks enough diagnostic detail, so reproducing, profiling, isolating the bottleneck, and validating a safe performance fix may span multiple subsystems. The left issue appears comparatively localized to configuration propagation and consistency checks.
#0 of 0 · 31d18h23m4s ago · #import:https:::github.com:berriai:litellm post #2475
-/https://github.com/berriai/litellm/issues/289074:1-/https://github.com/berriai/litellm/issues/34104⭐
The left task has substantially higher engineering risk because it spans asynchronous lifecycle coordination, failure recovery, queue durability, shutdown behavior, and regression testing. The right task appears narrower and would primarily require profiling followed by a targeted performance fix.
#0 of 0 · 31d17h56m24s ago — current · #import:https:::github.com:berriai:litellm post #2931
-/https://github.com/berriai/litellm/issues/213478:1-/https://github.com/berriai/litellm/issues/34104⭐
The left issue spans specification ingestion, schema validation, provider normalization, streaming and compatibility test infrastructure, and broad regression coverage. The right issue appears localized to profiling and optimizing a slow command, with scope and root cause still narrow.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search