Last year, at the 2016 LLVM dev room, I presented ideas on how to improve LNTto make performance tracking of LLVM generated code easier. We've implementedmost ideas since, and we're happy to see that our ideas work out in practice:quite often, understanding the root cause for a performance regression nowtakes about 5 to 10 minutes of work, whereas before it typically took us halfa day to produce all data that is now recorded automatically. I intend to give a demo of how we use LNT at ARM's LLVM teams. I'll alsodiscuss how LNT is useful for other projects that need to track performance ofgenerated code. LNT is starting to be used by at least also some GCC, java jitand even a Verilog-to-C++ compiler teams. I'll also give the necessary pointers on what you need to get started on LNTfor your own projects.