Who it is forAn inference engineer serving a Delta-rule model under concurrent requests, where fixed-size state still adds up in memory.
The problemRecurrent state memory grows with concurrency, and uniform low-bit quantization adds errors to every state update.
The outcomeAn OpenAI-style local endpoint, served from SGLang, that stores recurrent state in the STEP Quant 6-bit format.
What you need first
- Model checkpoints for a supported model, such as Qwen3.8-27B, placed on disk
- A CUDA toolkit and NVIDIA GPUs (the Qwen example uses four GPUs; the paper used NVIDIA A800 GPUs)
- Python with the tested stack: SGLang 0.5.12, PyTorch 2.11.0, Triton 3.7.1
- A clone of the repository, run from its root
Steps
- Run
bash scripts/reuse_sglang_env.sh /path/to/sglang-envandbash scripts/reuse_calibration_env.sh /path/to/qwen-env qwento prepare the environments. - Run
.venv-eval/bin/python -m stepquant.reproduction --models qwen --formats stepquant6 --devices 0,1,2,3to produce the calibrated plan at artifacts/reproduction/plans/qwen-stepquant6.pt. (inferred, check the README) - Run
CUDA_VISIBLE_DEVICES=0,1,2,3 .venv-serving/bin/python -m stepquant.sglang --model-path /path/to/Qwen3.8-27B --tp-size 4 --state-format stepquant6 --plan artifacts/reproduction/plans/qwen-stepquant6.pt --attention-backend triton --served-model-name stepquant --host 127.0.0.1 --port 31080. (inferred, check the README) - Send a test request to the server on 127.0.0.1 port 31080 and confirm it returns a completion.
Prompt for your agent
Using the STEPQuant repo at <repo_path>, calibrate a stepquant6 plan for the model at <model_path> and start the SGLang server with --state-format stepquant6. Report the server URL and the text of one test completion, and verify the server log shows the stepquant6 state format was loaded.
Caveat. The README's serving stack is pinned to SGLang 0.5.12, PyTorch 2.11.0, and Triton 3.7.1, and the example needs four GPUs, so other setups are not covered by the README.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page