• Home
Name
Date
Size
#Lines
LOC

..--

BUILD.gnD03-May-20242.6 KiB10597

README.mdD03-May-2024536 1610

httpd.ccD03-May-202414.6 KiB414314

httpd.hD03-May-20241.3 KiB3911

proto_ring_buffer.ccD03-May-20246.4 KiB189115

proto_ring_buffer.hD03-May-20245.2 KiB14035

proto_ring_buffer_unittest.ccD03-May-20247.4 KiB233167

query_result_serializer.ccD03-May-20249.9 KiB270165

query_result_serializer.hD03-May-20243.7 KiB10243

query_result_serializer_benchmark.ccD03-May-20243.2 KiB9769

query_result_serializer_unittest.ccD03-May-202415.9 KiB456376

rpc.ccD03-May-202412.1 KiB352273

rpc.hD03-May-20244 KiB10339

wasm_bridge.ccD03-May-20245.1 KiB13876

README.md

1# TraceProcessor RPC
2
3This directory contains the RPC interfaces to use the Perfetto Trace Processor
4remotely (i.e. not just in-process). It consists of two targets:
5
6## `wasm_bridge`
7
8The WASM (Web Assembly) interop bridge. It's used to call the Trace Processor
9from HTML/JS using WASM's `ccall`.
10
11## `httpd`
12
13The HTTP RPC module. It exposes a protobuf-over-HTTP RPC interface that allows
14interacting with a remote trace processor instance. It's used for special UI
15use cases (very large traces > 2GB) and for python interoperability.
16