tp: match a GLOB against the pool once per pattern **Why** `filter::StringFilterGlob` matches every row's string when it is given fewer rows than the pool holds strings, and matches every string in the pool once otherwise. `Filter` hands it one batch at a time, always fewer rows than the pool, so a scan of a large table with a GLOB matched every row. Stdlib tables built that way took 3 ms more each than on the interpreter, which hands it the whole table at once. A GLOB is also often the inner side of a join, run once per outer row with the same pattern, so compiling it and matching the same strings again on every lookup made those joins slower too. **Changes** - `Filter` keeps, for each GLOB condition, the compiled pattern and how many rows it has matched. A string's match depends only on the pattern, so this is kept from run to run until the pattern changes. - Rows are matched one at a time until as many have been as a quarter of the pool's strings. Then every string in the pool is matched in one pass, as the interpreter does for a large input, and each row after is a bit test. - A pattern without wildcards still compares string ids. **Testing** - New `FilterTest.GlobMatchesThePoolOnceForAPattern`, `GlobForgetsMatchesWhenThePatternChanges` and `GlobMatchesRowsOneAtATimeOverALargePool`. - `perfetto_unittests` and all diff tests pass.
Perfetto is an open-source suite of tools for recording, visualizing and analyzing traces: timelines of what software and the system under it were doing. It is the default tracing system for Android and Chromium. System-wide recording works on Android and Linux. The tracing SDK, the UI and Trace Processor also run on macOS and Windows.
perf, Firefox Profiler, macOS Instruments, pprof, systrace, Fuchsia and more.Open an example Android trace without installing anything, or drag your own trace file onto ui.perfetto.dev.
On Android, with a device connected over adb:
curl -O https://raw.githubusercontent.com/google/perfetto/main/tools/record_android_trace python3 record_android_trace -o trace.pftrace -t 10s sched freq gfx view am wm
The trace opens in the Perfetto UI when recording finishes.
On Linux, record scheduling activity with tracebox:
curl -LO https://get.perfetto.dev/tracebox && chmod +x tracebox curl -LO https://raw.githubusercontent.com/google/perfetto/main/test/configs/scheduling.cfg sudo ./tracebox -o trace.pftrace --txt -c scheduling.cfg
For Chrome, use the recording page in the UI. To trace your own app, see in-app tracing.
curl -LO https://get.perfetto.dev/trace_processor && chmod +x trace_processor ./trace_processor query trace.pftrace \ "SELECT name, COUNT(*) AS cnt FROM slice GROUP BY name ORDER BY cnt DESC LIMIT 10"
Or from Python:
pip install perfetto
from perfetto.trace_processor import TraceProcessor tp = TraceProcessor(trace='trace.pftrace') print(tp.query('SELECT ts, dur, name FROM slice LIMIT 10').as_pandas_dataframe())
ftrace. (Linux cookbook)chrome://tracing, for debugging the browser, V8 and Blink. (Chrome tracing)Not sure where to start? How do I start using Perfetto? picks a path based on what you want to do.
Perfetto is a collection of components that work together:
traced, traced_probes) collect data from many processes and the kernel into a single trace file.See the documentation for the full picture.
See Community and getting help for more. We follow Google's Open Source Community Guidelines.
Contributions are welcome. The contributor guide covers building, testing and sending pull requests.
The Debian packaging of Perfetto is maintained in the Debian Perfetto Salsa repository.
Apache 2.0. See LICENSE for details.