Energy as a first-class software design metric
We define software performance engineering (SPE) as “making software run fast or otherwise consume few resources such as time, storage, energy, network bandwidth, etc.” I’m focusing on energy today.
Fastcode
Making it easy to do software performance engineering.
Live Last read · last published · next check
Latest posts
Stinging Stragglers: Accelerating SSSP with Priority-Aware Work Stealing
[With this post, Fastcode welcomes Marco D’Antonio to the ranks of our contributors.
Co-evolution of algorithms, compilers, and hardware for performance
A Fastcode workshop at PPoPP-26
"Machine programming" vs. "ML for code"
Because moving fast is not enough
Three areas where AI can help SPE
In an earlier post, Bruce talked about how the weight of improving computer performance has shifted to software, algorithms, and hardware architecture, and how that shift makes Software Performance Engineering (SPE) more important than ever in the post-Moore world.
Harnessing the Power of LLMs for Software Performance Engineering
As someone who has spent decades optimizing parallel algorithms and wrestling with the complexities of high-performance computing, I'm constantly amazed by how the landscape of performance engineering continues to evolve.
Another look at comparing task-parallel programming platforms
I’d like to welcome Tsung-Wei (TW) Huang to the ranks of Fastcode contributors.
The three ingredients to making performance engineering easier and more fun
Given two "alternatives" X and Y, your next question makes all the difference.
Separating mechanism from policy: lock-free locks
Sometimes your program can have its cake and eat it too
Announcing OpenCilk 3.0
Making it easier for you to write fast programs in your favorite IDE