DNS: Spaghetti: Experimental node query builder

Note: This is an experiment representing my vision for how a
query builder should be architected and how it should look and feel.

- On-node configuration (no sidebar). This puts the node config right
  where the graph is and avoids mousing around, while also making it
  easier to read the graph as all the information is right there.
- Immutable (immer managed) node configuration allowing for simple
  and efficient undo/redo, and change detection.
- JS-side column name and type interence.
- JS-side materialization - no TP based serialization backend. Much
  simpler and just as effective + node highlighting while it's
  materializing.
- SQL folding, resulting in much more readable SQL code generation.
- Stable configs - when a node is detached from its parent, instead
  of forgetting its internal config its retains it and matches back
  columns via name when reconnected. If no such col name exists,
  highlight the column field in yellow for easy debugging.
- Node style:
  - Color coded titlebars with always visible names. This makes the
    graph much easier to interpret as there is a clear separation
    between the node title and its content.
  - Nodes are only draggable via their title bars, which allows for
    draggable elements within the body of the node.
  - Inputs and outputs are constrained to the left and right edges,
    resulting in more pleasing connection beziers.
- Very experimental LLM integration built in - allows asking LLMs to
  view and build graphs for you.

Change-Id: I6c93d9463982675e0e663e87fa05a9156907d1a7
67 files changed
tree: 15f5b7ef4544ed14890d724339da51057a73ce02
  1. .github/
  2. ai/
  3. bazel/
  4. build_overrides/
  5. buildtools/
  6. contrib/
  7. docs/
  8. examples/
  9. gn/
  10. include/
  11. infra/
  12. protos/
  13. python/
  14. sdk/
  15. src/
  16. test/
  17. third_party/
  18. tools/
  19. ui/
  20. .bazelignore
  21. .bazelrc
  22. .bazelversion
  23. .clang-format
  24. .clang-tidy
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gn
  30. .style.yapf
  31. Android.bp
  32. Android.bp.extras
  33. anrs.json
  34. binder.json
  35. binder2.json
  36. BUILD
  37. BUILD.extras
  38. BUILD.gn
  39. CHANGELOG
  40. CONTRIBUTORS.txt
  41. DIR_METADATA
  42. heapprofd.rc
  43. LICENSE
  44. meson.build
  45. METADATA
  46. MODULE.bazel
  47. MODULE.bazel.lock
  48. MODULE_LICENSE_APACHE2
  49. OWNERS
  50. OWNERS.github
  51. perfetto.rc
  52. perfetto_flags.aconfig
  53. PerfettoIntegrationTests.xml
  54. persistent_cfg.pbtxt
  55. README.chromium
  56. README.md
  57. TEST_MAPPING
  58. traced_perf.rc
  59. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is an open-source suite of SDKs, daemons and tools which use tracing to help developers understand the behaviour of complex systems and root-cause functional and performance issues on client and embedded systems.

It is a production-grade tool that is the default tracing system for the Android operating system and the Chromium browser.

Core Components

Perfetto is not a single tool, but a collection of components that work together:

  • High-performance tracing daemons: For capturing tracing information from many processes on a single machine into a unified trace file.
  • Low-overhead tracing SDK: A C++17 library for direct userspace-to-userspace tracing of timings and state changes in your application.
  • Extensive OS-level probes: For capturing system-wide context on Android and Linux (e.g. scheduling states, CPU frequencies, memory profiling, callstack sampling).
  • Browser-based UI: A powerful, fully local UI for visualizing and exploring large, multi-GB traces on a timeline. It works in all major browsers, requires no installation, and can open traces from other tools.
  • SQL-based analysis library: A powerful engine that allows you to programmatically query traces using SQL to automate analysis and extract custom metrics.

Why Use Perfetto?

Perfetto was designed to be a versatile and powerful tracing system for a wide range of use cases.

  • For Android App & Platform Developers: Debug and root-cause functional and performance issues like slow startups, dropped frames (jank), animation glitches, low memory kills, and ANRs. Profile both Java/Kotlin and native C++ memory usage with heap dumps and profiles.
  • For C/C++ Developers (Linux, macOS, Windows): Use the Tracing SDK to instrument your application with custom trace points to understand its execution flow, find performance bottlenecks, and debug complex behavior. On Linux, you can also perform detailed CPU and native heap profiling.
  • For Linux Kernel & System Developers: Get deep insights into kernel behavior. Perfetto acts as an efficient userspace daemon for ftrace, allowing you to visualize scheduling, syscalls, interrupts, and custom kernel tracepoints on a timeline.
  • For Chromium Developers: Perfetto is the tracing backend for chrome://tracing. Use it to debug and root-cause issues in the browser, V8, and Blink.
  • For Performance Engineers & SREs: Analyze and visualize a wide range of profiling and tracing formats, not just Perfetto's. Use the powerful SQL interface to programmatically analyze traces from tools like Linux perf, macOS Instruments, Chrome JSON traces, and more.

Getting Started

We‘ve designed our documentation to guide you to the right information as quickly as possible, whether you’re a newcomer to performance analysis or an experienced developer.

  1. New to tracing? If you're unfamiliar with concepts like tracing and profiling, start here:

  2. Ready to dive in? Our “Getting Started” guide is the main entry point for all users. It will help you find the right tutorials and documentation for your specific needs:

  3. Want the full overview? For a comprehensive look at what Perfetto is, why it's useful, and who uses it, see our main documentation page:

Debian Distribution

For users interested in the Debian distribution of Perfetto, the official source of truth and packaging efforts are maintained at Debian Perfetto Salsa Repository

Community & Support

Have questions? Need help?

We follow Google's Open Source Community Guidelines.