Skip to content

Agents load testing results#182

Draft
jennsun wants to merge 9 commits intodatabricks:mainfrom
jennsun:agents-load-testing-results
Draft

Agents load testing results#182
jennsun wants to merge 9 commits intodatabricks:mainfrom
jennsun:agents-load-testing-results

Conversation

@jennsun
Copy link
Copy Markdown
Contributor

@jennsun jennsun commented Apr 3, 2026

Across all 5 runs (20 config-runs each):
┌─────────┬──────────────┬─────────┐
│ Compute │ Avg Peak QPS │ Avg QPS │
├─────────┼──────────────┼─────────┤
│ Medium │ 123.5 │ 45.5 │
├─────────┼──────────────┼─────────┤
│ Large │ 278.0 │ 100.1 │
└─────────┴──────────────┴─────────┘

Large is ~2.2x medium on both peak and average QPS.

Recommendations:

  • Medium: 2 workers — clearly the best, 33% higher peak QPS
    than 4 workers. More workers on medium compute likely
    causes contention on the limited CPU/memory, so the
    overhead of managing extra processes outweighs the
    parallelism benefit.
  • Large: 6-10 workers — the differences are small (268-288,
    within ~7%), so any of these work. 10w edges out slightly
    but it's within noise. I'd recommend 8 workers as a safe
    default since it's in the middle of the plateau and avoids
    the slight dip at 12w.

The takeaway: on smaller compute, fewer workers is better
(less overhead). On larger compute, there's a sweet spot in
the middle — adding workers beyond that introduces
diminishing returns and eventually contention.

So it looks like on average we’re seeing large compute with ~2x medium on peak (278 peak avg vs 123.5 avg) and average QPS, but more workers is not necessarily always better

jennsun and others added 8 commits March 31, 2026 08:51
Load test results for agent app with 1000ms simulated latency across
medium (2/4/6/8 workers) and large (6/8/10/12 workers) configurations,
including dashboard, Locust reports, and analysis.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jennsun jennsun changed the title Agents load testing results - agent_app_1000_load_test Agents load testing results Apr 6, 2026
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.

1 participant