Initial trace-based startup metric in AOSP
- Partitions the trace into spans based on the initial intent
- Correlates these spans with an actual launching event
- Breaks down main thread by task state
Bug: b/132775271
Change-Id: I14765c5591f787f269d47b5fe217e458de2eb28e
diff --git a/src/trace_processor/trace_storage.cc b/src/trace_processor/trace_storage.cc
index a0892b4..2731638 100644
--- a/src/trace_processor/trace_storage.cc
+++ b/src/trace_processor/trace_storage.cc
@@ -124,6 +124,8 @@
nestable_slices_.start_ns().end(), &start_ns, &end_ns);
MaybeUpdateMinMax(android_log_.timestamps().begin(),
android_log_.timestamps().end(), &start_ns, &end_ns);
+ MaybeUpdateMinMax(raw_events_.timestamps().begin(),
+ raw_events_.timestamps().end(), &start_ns, &end_ns);
if (start_ns == std::numeric_limits<int64_t>::max()) {
return std::make_pair(0, 0);