~/talk

LTTng for full stack tracing

Talkat Qt World Summit 2019 · 2019-11-04..11-06· [observability, devops-and-delivery]
links:none on file
slides:none on file

Full-stack tracing using LTTng plus Qt user-space trace points and a CTF→Chrome trace converter identifies exact causes of slow startup: kernel sched switches, syscalls, plugin loads and mmap activity show that disk-heavy debug logging and loading unneeded image plugins — on an NVIDIA Tegra X1 Yocto build — cause multi-second delays; raising I/O priority and stripping plugins drops startup from ~5s to ~1s. Built a tracegen for Qt tracepoints and a CTF-to-JSON pipeline, records 20s full-system traces ~10–218 MB binary (~2 MB JSON) with negligible overhead.

AI-written summary · about

  1. 0:00Introduction to full-stack tracing
  2. 2:11Motivating real-world example
  3. 7:57Why LTTng for tracing
  4. 9:43Setting up LTTng on device
  5. 11:10Recording a system trace
  6. 14:28Analyzing trace data
  7. 17:00CTF2: Custom trace visualization
  8. 20:15Key trace points explained
  9. 22:45Future of tracing in Qt
  10. 23:45Performance impact and overhead
  11. 24:53Q&A and conclusion
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.