Profilers, flamegraphs, benchmarks and caches: find the slow part first, then fix only that.
Which release profile settings change speed, size and compile time: lto, codegen-units, opt-level, panic abort, strip and debug. A table of effects, a recommended starting point and how to measure.
Every v[i] checks the index. In many loops the optimizer proves the check unnecessary and removes it. Learn when that happens, how to help it and why unchecked indexing is rarely worth it.
Criterion gives statistics and plots on stable Rust; Divan gives a lighter attribute-based API with allocation counting. Compare setup, output, features and pitfalls.
Profiles are named sets of compiler settings. Learn dev, release, test and bench, the keys that matter, per-package overrides and how to define a custom profile that inherits from release.
Talk to Redis from Rust with redis-rs: a multiplexed async connection through ConnectionManager, commands, pipelines, expiry, pub/sub and handling disconnects.
Rust iterator chains compile to the same machine code as hand-written loops in most cases. See where they tie, where they differ and the few places where a plain loop is clearer or faster.
Vec::with_capacity avoids repeated regrowth, and clear keeps capacity for reuse. See how growth works, when pre-sizing helps and how to avoid holding oversized buffers forever.
Find where a Rust program allocates with a profiler or an allocation counter, then remove the hot ones: reuse buffers, borrow, pre-size and avoid format in loops.
Shrink a Rust binary in steps: strip symbols, size optimization, LTO, panic abort, dependency pruning and cargo bloat to find what takes the space.
codegen-units splits a crate into parallel pieces and opt-level picks how hard LLVM works. See the defaults, the trade-offs and the settings for speed or size.
LTO lets the compiler optimize across crates and often shrinks and speeds a binary, at the cost of build time. See thin, fat and off, and how to measure the trade.
A pool that is too small queues requests and one that is too large exhausts the database. Learn how to size it from your server's limits, set timeouts and spot the symptoms.
We send one email when a new post is published. No spam.