✳flâneur — a map of the web's best reading

sled theoretical performance guide | sled-rs.github.io

sled.rs · 11,260 words · saved by 1 readers

This guide covers timeless ideas that are helpful to keep in mind while working with systems where performance matters. Many of these ideas are fairly “durable” and will apply regardless of what hardware, programming language, operating system, or decade you are working in. Stay tuned for follow-up articles that will drill into hardware and more Rust-specific techniques. Skip to the table of contents if you don’t like intros. There’s some foul language in here. Enjoy! Ok, now that the executives are gone, it is time to party. Let’s put on some nice music. Take a deep breath. Let it out. The year is 2020. and we are utterly fucked. Supposedly we are here reading this article because we “like computers” or something but let’s be clear about one thing - you’re not here because of that. I know. You know. We all know. You couldn’t give two fried pennies about computers if they didn’t help you feel the things you so desperately need to feel. You’re here, ultimately, because of control. Your

sled theoretical performance guide | sled-rs.github.io sled theoretical performance guide This guide covers timeless ideas that are helpful to keep in mind while working with systems where performance matters. Many of these ideas are fairly “durable” and will apply regardless of what hardware, programming language, operating system, or decade you are working in. Stay tuned for follow-up articles that will drill into hardware and more Rust-specific techniques. Skip to the table of contents if you don’t like intros. There’s some foul language in here. Enjoy! executive summary make it work, then

Explore this link on the map →

related reading