tp: optimize key loading and collision probing in GroupTable

**Summary**

Fast-path contiguous key loading and validity word scanning in `GroupTable::Load`, hoist `Salt(hash)` calculation out of collision loops, and eliminate unnecessary memory reads on hash collision probes in `FindValues` and `FindOrCreate`.

**Why**

`GroupTable` powers key grouping and deduplication across executor operators, including `DISTINCT` (`Distinct`), `GROUP BY` (`HashAggregate`), and `GROUPED SORT` (`GroupedSort`):
- `GroupTable::Load` gathered keys element-by-element using `column.Index(selection[row])` and checked validity bit-by-bit via `validity->is_set()` on every row, even when batches were contiguous (`selection.prefix()`). For `int64_t` keys, contiguous batches can be loaded with a single `memcpy`, and validity bits can be tested in 64-row words via `ReadBits(start + row, n)`.
- In `FindValues` and `FindOrCreate`, `Salt(hash)` was repeatedly recalculated on every probe collision, and `FindValues` dereferenced `group_rows_` to read `stored[1]` and `stored[0]` before verifying whether `Salt(slot) == Salt(hash)`. Because `Salt(slot)` stores the top 16 bits of the hash, 99.998% of hash probe collisions can be rejected immediately without dereferencing `group_rows_` and incurring cache line misses.
- `(slot & ~Salt(slot)) - 1` performed multiple shifts and bitwise operations to extract the group number from `slot`, which can be masked directly via `(slot & kGroupMask) - 1`.

**Changes**

- In `Gather`, fast-path contiguous selections: copy `int64_t` keys directly via `memcpy`, and iterate contiguous arrays without index indirection for `uint32_t`, `int32_t`, and `double` keys.
- In `GroupTable::Load`, read validity bits 64 rows at a time using `validity->ReadBits()` when `selection.prefix()` is true, skipping entire 64-row blocks when all rows are valid and using `CountTrailZeros64` for sparse nulls.
- In `FindValues` and `FindOrCreate`, hoist `Salt(hash)` computation outside the probe loop and guard `group_rows_` dereferences behind the `Salt(slot) == salt` check.
- Fast-path 1-key and 2-key comparisons in `GroupTable::Equal` and hash combining in `GroupTable::Hash`.

**Benchmarks**

Release benchmarks on `out/linux_clang_release`:
- `BM_Distinct/0/512/1/16` (clustered int64): 215,411 ns -> 141,534 ns (1.52x faster, 34% reduction)
- `BM_Distinct/0/262144/0/128` (256k distinct int64): 14.35 ms -> 9.10 ms (1.58x faster)
- `BM_Distinct/1/512/0/16` (two int64 keys): 540,280 ns -> 428,601 ns (1.26x faster)
- `BM_Distinct/2/512/0/16` (string): 248,961 ns -> 173,832 ns (1.43x faster)
- `BM_HashAggregate/8/1`: 177,756 ns -> 128,236 ns (1.39x faster)
- `BM_HashAggregate/512/1`: 233,426 ns -> 160,189 ns (1.46x faster, 31% reduction)
- `BM_HashAggregate/8192/1`: 605,924 ns -> 496,023 ns (1.22x faster)
- `BM_HashAggregate/32768/1`: 1,259,551 ns -> 997,989 ns (1.26x faster)
- `BM_GroupBy/0/512/0/16`: 476,048 ns -> 378,874 ns (1.26x faster)
- `BM_GroupBy/1/512/0/16` (nullable int64): 810,348 ns -> 624,191 ns (1.30x faster)

**Testing**

- `perfetto_unittests --gtest_filter="*GroupTable*:*Distinct*:*HashAggregate*:*GroupedSort*:*Exec*"` (45 passing tests).
- `diff_test_trace_processor.py` on distinct and aggregate tests (17 passing tests).
- Verified `SELECT DISTINCT` and `GROUP BY` execution on `test/data/example_android_trace_30s.pb`.
2 files changed
tree: e773619773f6332ac41e3bd27e95320a605d6e96
  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. BUILD
  34. BUILD.extras
  35. BUILD.gn
  36. CHANGELOG
  37. CONTRIBUTORS.txt
  38. DIR_METADATA
  39. heapprofd.rc
  40. LICENSE
  41. meson.build
  42. METADATA
  43. MODULE.bazel
  44. MODULE.bazel.lock
  45. MODULE_LICENSE_APACHE2
  46. OWNERS
  47. OWNERS.github
  48. perfetto.rc
  49. perfetto_flags.aconfig
  50. PerfettoIntegrationTests.xml
  51. persistent_cfg.pbtxt
  52. README.chromium
  53. README.md
  54. TEST_MAPPING
  55. traced_perf.rc
  56. 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.