gpustack / gpustack/benchmark-runner
macOS: benchmark run can hang indefinitely with default multiprocessing/data loader settings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Description
On macOS, benchmark_runner may hang indefinitely during benchmark run when using default runtime settings.
The process reaches the benchmark phase but does not make progress for several minutes (or longer), and no explicit error is raised.
Environment
- OS: macOS (Apple Silicon)
- Python: 3.11
- benchmark-runner: v0.0.2
Backend: OpenAI-compatible HTTP endpoint
Data: synthetic (prompt_tokens=...,output_tokens=...)
Reproduction
python -m benchmark_runner.main benchmark run \
--target http://<server>:<port> \
--sample-requests 0 \
--output-dir .cache \
--outputs full.json \
--processor <local_tokenizer_path> \
--data prompt_tokens=8192,output_tokens=100 \
--profile constant \
--rate 1 \
--max-requests 10
Expected behavior
Benchmark starts and either: progresses normally, or fails fast with a clear error.
Actual behavior
The command appears stuck/hung (often at the benchmark stage) without completion or explicit failure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the python -m benchmark_runner.main benchmark run entry point and reproduce the hang on macOS with the command shown, focusing on the default multiprocessing and data-loader settings. Trace the benchmark phase to determine why it neither progresses nor fails; done means the run completes normally or exits with a clear error under those defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100