You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After correcting the benchmark methodology, v5 is consistently 24–37x faster than v4:
Target
v4 (TypeScript)
v5 (Rust)
Speedup
fixtures (548 files, 1.5 MB)
1.03s
0.03s
34.3x
svelte (9K files, 38 MB)
15.80s
0.43s
36.9x
CopilotKit (17K files, 159 MB)
82.89s
3.44s
24.1x
Key observations
Startup overhead: v5's native binary has near-zero startup cost. v4's Node.js runtime adds ~1s even for tiny fixtures.
Scaling: v5 scales well from small to large codebases. CopilotKit (159 MB) takes only 3.4s. v4 takes 83s on the same target.
CPU utilization: v5's higher user time relative to real time (e.g., CopilotKit: 7.3s user vs 3.4s real) shows effective multi-threading. v4 is single-threaded (user ≈ real).
Consistency: v5 has tighter variance across all runs. On CopilotKit, v5's std dev is 0.7s (20% of mean) vs v4's 4.1s (5% of mean, but absolute variation is much larger).
File scanning differences: v4 with --no-gitignore analyzes more files than v5 on svelte (11,672 vs 4,322) because v5's gitignore handling differs. This means v5 is even more efficient per-file analyzed than the raw speedup numbers suggest.
Detection accuracy: v5 finds more clones on large codebases (1,055 vs 903 on svelte, 22,487 vs 12,272 on CopilotKit), likely due to different token counting and the maxSize default behavior.