Topics / Better algorithms
Performance topic
Better algorithms
Changing the algorithm or data structure: a lower complexity class, an index instead of a scan, an incremental update instead of a recompute. Usually the largest speedups in the database, and the ones a profiler alone does not suggest.
Examples from real commits
Languages
- C++1,671
- C606
- Rust471
- Python437
- CUDA244
- Go155
Hardware
- CPU1,435
- NVIDIA GPU687
- GPU449
- x86341
- ARM117
Fields
- data & compression1,294
- graphics1,095
- math1,056
- general976
- compilers975
Where these come from
Repositories with the most techniques on this topic in the database:
thofma/Hecke.jl · 25mratsim/constantine · 18nmap/nmap · 14golang/go · 13flintlib/flint · 12mruby/mruby · 12colmap/colmap · 12Nemocas/Nemo.jl · 12angr/angr · 12libigl/libigl · 12
Ask Claude for the full answer
Each technique comes with its bottleneck, measured speedup, trade-offs, conditions and the commit or paper behind it, served to Claude through MCP.
claude mcp add --transport http adtomic https://www.adtomic.co/mcp
Related topics
Precomputation and memoizationAvoiding allocationsEarly exit and pruningBit tricks and strength reductionBatching