News for hackers. Stuff that matters.
Re:Principles for Fast Tokio Applications by jeffbee on Monday September 14, 2026 @12:07PM (#49699249)
All of the significant server applications I have encountered in the industry have suffered from the same problem, which surprised their authors but seemed obvious to me: the application was spending the majority of its CPU time doing meta-work like entering and leaving epoll, stealing work from itself, etc. There are principles for writing Tokio servers and these are good points in the OP but I think they are little-known and too easy to violate.
Re:Principles for Fast Tokio Applications by cube00 on Monday September 14, 2026 @12:18PM (#49699443)
I can't say I'm surprised when I see the 100+ function stack traces that Axum built on Tokio produces.

Before you say Axum is "holding it wrong" the project lives under the tokio-rs GitHub org.

Re:Principles for Fast Tokio Applications by rusbus on Monday September 14, 2026 @01:59PM (#49701125)
Note that most of those end up getting inlined in practice
Re:Principles for Fast Tokio Applications by prydt on Monday September 14, 2026 @06:46PM (#49705289)
Do you have any references for these principles for writing Tokio servers? Or just a high level summary of what best practices look like?