Is your Rust program CPU bound? Here are the very first things you can do on Linux. First be sure the CPU really is the bottleneck. htop should tell you, or that aircraft-taking-off fan noise. Second isolate the part you are concerned about into a program (or unit test or benchmark) that you can run repeatably. Third, get some ballpark measurements by running one of these at least four times: time ./myprog perf stat -e task-clock ./myprog Build in release mode with link time optimization Add ...