perf(scan): AVX-512 + vpclmulqdq scanner backend
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, rust
- Domain
- ci-cd, performance
Research direction
Read src/scan/avx2.rs and src/scan/mod.rs, then run the proposed CPU-feature diagnostic in the CI workflow to establish whether vpclmulqdq is consistently available. If the prerequisite is met, done means adding the feature-gated AVX-512 path, dispatcher fallback, cross-check coverage, supported-runner validation, and benchmark evidence.
Written by the indexing model from the issue text.
Description
Context
Current scanner uses AVX2 + PCLMUL (128-bit). On CPUs supporting avx512bw + vpclmulqdq (Ice Lake / Sapphire Rapids / Zen 4+), a 128-byte chunk path could halve the loop iteration count.
Prerequisite: CPU support audit
This issue is gated on confirming that the project's actual build/CI hosts support vpclmulqdq. If not, ROI is 0 and the issue should be deferred indefinitely.
-
Local dev host: confirmed missing
vpclmulqdq(Skylake-X / Skylake-SP — has avx512bw but not vpclmulqdq). Cannot test locally. -
CI runners:
ubuntu-latestrunner CPUs vary by allocation. Add a one-line diagnostic to the workflow:- name: CPU features run: grep -oE '\b(avx2|avx512bw|vpclmulqdq|pclmulqdq)\b' /proc/cpuinfo | sort -uCollect output over several CI runs; only proceed if
vpclmulqdqis reliably present.
If CI runners do not reliably provide vpclmulqdq, the only path to validating this is paid larger-runners or self-hosted runners.
Proposal (pending CPU confirmation)
- New
src/scan/avx512.rsmirroringavx2.rswith 128-byte chunks - Dispatcher (
src/scan/mod.rs): AVX-512 → AVX2 → scalar fallback chain - New
avx512feature flag (default off) so release builds stay portable - Use
_mm512_clmulepi64_epi128for the inside-string prefix-XOR
Estimated impact
| est. speedup | |
|---|---|
CPUs with avx512bw + vpclmulqdq |
~1.5–2× scan throughput |
| Other CPUs | 0 (dispatcher falls back) |
Validation plan
-
scanner_crosscheckproptest extended to compare AVX-512 vs scalar - CI matrix on a runner confirmed to have
vpclmulqdq -
make bench3-run median on supported hardware
Recommendation
Last in the perf followup queue. The CPU support situation is uncertain; if it turns out CI runners don't have vpclmulqdq, this is dead code we maintain forever. Do the cheap wins (#5 memchr, #6 pooling, #7 PGO, #8 micro-opts) first.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from api7/lua-qjson
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100