PERFETTO-TRACE

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

Perfetto Trace Preview.

At a glance

How much Poka reads

B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-perfetto/src/main.rs (584 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has sample.perfetto-trace, read by no test. Covers .perfetto-trace and .pftrace. The tree walks the packets and shows the packet count, trace duration (from timestamps), size, the dominant data source, packet types by data source (track events, ftrace and others) and the track names from track descriptors. Judgement: B4: the trace is summarised by packet type and duration, but no event is decoded.

What Poka does not read

• Events are not decoded: no slices, counters, scheduling or ftrace events
• Process and thread descriptors are counted, not listed (judgement from the code)
• Compressed packets and interned data are not resolved
• The timeline is not drawn

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

• Perfetto trace processor (candidate; Apache-2.0; C++; https://github.com/google/perfetto) — Official C++ trace processor that ingests Perfetto traces and exposes them via SQL. Brings a native build, so no direct fit for wasm32-wasip1.
• perfetto (Python API) (candidate; Apache-2.0; Python; https://perfetto.dev/docs/analysis/trace-processor-python) — pip package loading .perfetto-trace/.pftrace through the trace processor and querying with SQL. Licence is of the repo; docs code samples are Apache-2.0.

Sources

• parsers/poka-perfetto/src/main.rs
• parsers/poka-perfetto/plugin.json