π Community Benchmark Challenge β Share Your Hardware Results vs llama.cpp #3
shifulegend
started this conversation in
Show and tell
Replies: 1 comment
-
|
Dropping the reference numbers here to seed the table. Intel Xeon (Emerald Rapids, 4-core, 32GB DDR5-5600, single-channel):
Third-party verification: https://openbenchmarking.org/result/2606207-SHIF-PROJECT42 Intel i5-11300H (Tiger Lake, 4-core, 16GB DDR4):
The MoE number is honest - DeepSeek-V2-Lite's expert scatter is a DRAM bandwidth problem we haven't solved yet. BitNet and dense GGUF are where the speedups are. For submissions: mention CPU, core count, DRAM type/config, and include the llama.cpp baseline on the same machine. Cross-machine tok/s comparisons are hard to interpret without knowing the DRAM bandwidth tier. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Why We're Asking
Project Zero is a from-scratch CPU-only LLM inference engine in C β no GPU, no Python, no external dependencies. We've benchmarked extensively on two machines (Intel i5-11300H laptop and a Xeon server), but every CPU is different. Memory bandwidth, L3 cache size, SIMD tier, DRAM configuration β all of these affect inference speed in ways that are hard to predict analytically.
We're building a community benchmark table to:
This is a crowdsourced leaderboard. Your result matters.
What to Run
Step 1 β Clone and build (30 seconds)
git clone https://github.com/shifulegend/project-zero cd project-zero make releaseRequirements: GCC or Clang, pthreads, libm. Nothing else.
Step 2 β Get a model
BitNet (recommended β fastest, smallest download):
DeepSeek-V2-Lite-Chat GGUF (tests MoE path):
Step 3 β Run the benchmark
Step 4 β Run llama.cpp on the same model (for comparison)
Step 5 β Post your results below using this template
π Result Template
Copy and fill this in your reply:
π Community Results β Running Table
I'll update this table as results come in.
Reference: Our Own Benchmarks (Baseline)
Key observation: On a memory-bandwidth-constrained laptop, llama.cpp is ahead. On a server with high L3 and AVX-512 VNNI, Project Zero wins by 1.83Γ. We want to know where your machine lands.
What We'll Do With Your Data
BENCHMARK_REPORT.mdin the repoKnown Quirks to Watch For
cmake -B build && cmake --build build --config Release. Let us know if you hit build issues.Questions?
Ask below β happy to help you get the build working or interpret your results.
Every data point helps. Even "it crashed on my machine" is useful information.
Beta Was this translation helpful? Give feedback.
All reactions