I contributed LTO-related changes to many open-source projects, and had a lot of interesting discussions with their maintainers about LTO. In this talk, I want to share with you my experience.

Link-Time Optimization (LTO) is a compiler optimization technique that helps a lot with optimizing software beyond the default Release profile. This optimization can be enabled by a single line in your Cargo.toml file. But is it so easy in the real world?
I contributed LTO-related changes to many open-source projects, and had a lot of interesting discussions with their maintainers about LTO. In this talk, I want to share with you my experience. We will discuss the following topics:
* What is LTO? Why is it useful?
* What kinds of LTO do we have in Rust? With their pros and cons in different scenarios.
* LTO adoption state in the Rust ecosystem and what we can do with that.
* Common and not-so-common LTO issues and how to mitigate them.
* How to integrate LTO into your project properly.
* And of course answer all your questions about LTO!
After the talk, you will be much more prepared to optimize your Rust applications with LTO and avoid as much LTO traps as possible!
In this talk, we'll dive deep into what makes concurrency coordination costly, and explore some pathways to mitigate that cost.
This talk puts popular Rust rewrites to the test. We'll examine how these tools stack up against their battle-tested predecessors, looking at real-world performance, compilation times, binary sizes, feature completeness, and ecosystem maturity.
This talk explores building a complete self-hosted LLM stack in Rust: Paddler, a distributed load balancer for serving LLMs at scale, and Poet, a static site generator that consumes those LLMs for AI-powered content features.