cactus-compute / cactus-compute/cactus
How to reproduce the Needle benchmark numbers on Cactus?
- Dominant language
- C++
- Stars
- 6k
- Forks
- 503
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 4
Description
Hi Cactus team,
I am trying to reproduce the Needle performance numbers mentioned on the Hugging Face page:
https://huggingface.co/Cactus-Compute/needle
It says:
> In production, Needle runs on Cactus at 6000 toks/sec prefill and 1200 decode speed.
I tested Needle on the `align_needle_inference_logic` branch with the Cactus old-style INT4 weights format.
My setup:
- Device: NVIDIA Jetson Thor / ARM Linux
- Branch: `align_needle_inference_logic`
- Commit: `71fc11bc`
- Model format: `config.txt + *.weights`
- Quantization: INT4 weights, FP16 compute
My measured speed is around:
```text
prefill: ~1200 tok/s
decode: ~100-140 tok/s
```
Could you share the exact setup used to get the reported numbers?
Specifically:
Which device/hardware was used?
Which Cactus branch/commit was used?
Which model weights were used?
What benchmark command or script was used?
What input length and output length were measured?
Was this CPU-only, GPU, Apple NPU/ANE, Android NPU, or another backend?
Thanks,I look forward to hearing from you!
Contributor guide
Research direction
Start with the Hugging Face Needle page and the align_needle_inference_logic branch at commit 71fc11bc, then compare the reported setup with the Jetson Thor results in the issue. Identify the benchmark command or script, model weights, backend, hardware, and input/output lengths needed to reproduce the published prefill and decode numbers; done means those details are documented and the numbers are reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, huggingface, linux
- Domain
- embedded-iot, machine-learning, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100