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!
For infrastructure engineers, SREs, platform teams, and Rust developers who've felt the pain of configuration drift, failed deployments, and infrastructure code that simply doesn't scale safely.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.
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.
During this talk we'll build a basic, working async runtime using nothing more than a standard library. The point? To see it's approachable for mere mortals.