Create Basic Stress Tests for LM and HM

Open

#437 opened on Aug 7, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 55/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: cpp
Domain: testing

Research direction

Start by reviewing existing tests in the testing/integration folder and the Launch Manager and Health Monitor test setup. Run the current integration-test suite to see how processes and configuration are created. Done means at least one stress test for LM and one for HM is available there; measuring activation time is optional.

Written by the indexing model from the issue text.

Description

good first issue

What

Launch Manager (LM) and Health Monitor (HM) could benefit from a set of basic stress tests. The goal is not to build a comprehensive benchmarking suite, but rather to increase confidence in the robustness and scalability of the system under heavier-than-usual workloads.

Launch Manager

As an initial stress test, we could create a scenario that starts 1024 processes (just because 1024 is a nice round number).

Possible setup:

512 reporting processes
512 native processes
Minimize the number of unique executables and launch the same executable multiple times through configuration
Generate the large JSON configuration programmatically to avoid excessive duplication and simplify maintenance

Bonus: Measure and record run-target activation time as the number of processes increases (execute this test with different number of processes).

Health Monitor

Similarly, we could design a stress tests focused on Health Monitor scalability.

Acceptance Criteria (DoD)

At least one stress test for LM and one for HM is available in testing/integration folder.

How

No response

Dominant language: C++
Stars: 6
Forks: 34
Avg merge: 1d 23h
Merged PRs (30d): 83

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues