Hi Abhijith, could you give this a first review before I send it to others?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
TaskTraits.BEST_EFFORT,This will end up blocking startup if it takes too long. Shouldn't this be higher priority?
+ AwFeatures.WEBVIEW_EARLY_PERFETTO_INITCurious, does it make sense to consolidate all our perfetto flags into one flag and use feature params to select different behaviours? That way, I don't think we have to worry about a situation where multiple feature params are enabled at the same time?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This will end up blocking startup if it takes too long. Shouldn't this be higher priority?
Good point. Adjusted to USER_VISIBLE
Curious, does it make sense to consolidate all our perfetto flags into one flag and use feature params to select different behaviours? That way, I don't think we have to worry about a situation where multiple feature params are enabled at the same time?
Possibly, but it would still only have one variant tested at a time, and the flags UI does not support params afaik, so this approach allows the flag UI to select each arm.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hi Torne, would you mind taking a look at this? It is more complex than the previous CL that added an experiment for background startup because it makes sure that Perfetto is in fact initialized before it proceeds with main thread startup.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (g_initializing_perfetto_on_background_thread) {If the call to InitPerfetto has been posted to a background thread then I don't think anything guarantees that it will have reached the point of setting this variable to true before this function is called?
I think you would need to always signal the event and always wait on it, and only read `g_initializing_perfetto_on_background_thread` *after* successfully waiting for it if you want to know whether it was done on the background thread or not for the purposes of the metric.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |