Lines Matching full:traces

5 interactive queries on large sets (up to ~1000) of traces._
17 ## Loading traces
19 …(http://goto.corp.google.com/perfetto-btp-load-internal) for how to load traces from Google-intern…
21 The simplest way to load traces in is by passing a list of file paths to load:
26   'traces/slow-start.pftrace',
27   'traces/oom.pftrace',
28   'traces/high-battery-drain.pftrace',
35 all traces in a directory:
39 files = glob.glob('traces/*.pftrace')
44 NOTE: loading too many traces can cause out-of-memory issues: see
47 A common requirement is to load traces located in the cloud or by sending
48 a request to a server. To support this usecase, traces can also be loaded
82 A common requirement is for all of the traces to be flattened into a
99 the notion of "paths" to traces from the filesystem. Instead, the URI
114 would indicate that traces should be fetched using the protocol `gcs`
115 ([Google Cloud Storage](https://cloud.google.com/storage)) with traces
122 the bytes of the traces to be able to parse and query them. The job of
125 to lookup the traces to be parsed.
136 making queries fast (<1s) even on hundreds of traces.
138 This also means that the number of traces you can load is heavily limited by
140 average trace size is S and you are trying to load N traces, you will have