Status Update
Comments
cc...@google.com <cc...@google.com> #2
Thanks for the report and all the details. Are you only seeing these build speed issues on CI? What's the build speed like in local development?
It would be great if you could share the compiler dump file with
ca...@google.com <ca...@google.com> #3
Are you only seeing these build speed issues on CI? What's the build speed like in local development?
Hi, we usually don't run minified builds on our local environments, mainly because of the time it takes to run it and the amount of ram it would require.
I don't want to complain even more about it, but I'm sure you are already aware of the constraints that Android has. We already have the IDE taking +10GB, the Kotlin Compiler daemon (1-6GB depending on the compilation work needed), the Gradle daemon (usually around 14G at the end of the build). If we were to enable R8 on local builds, this would render local machines (even our beefy M1s) unable to use for minimum 15 minutes each time we would want to run the app. Devs will turn this off immediately.
A good starting point would be to check if there are any passes that take up an unusual amount of time.
Do you mean running the compiledump.py
? Is this what the dump will be used for? If so, can I do that locally without any external tool? I'd rather not share the dump if I can test it myself. If there is more to it, then I'll try to upload it somewhere safe.
Description
Component used: Version used: Devices/Android versions reproduced on:
If this is a bug in the library, we would appreciate if you could attach:
I want to use macrobenchmark to analyse launch animation of launcher.
However, launch animation is different with ordinary application animation.
take OPPO phone's launcher as a example( the first screenshot)
the launching animation has three layers :
starting window layer, which cover on the launched app layer be launched app layer, which will be shown after app launched and get screen shot of this app the launcher layer as background, which is blured and disappered
In the perfetto trace , we can see three actual frametimeline for three layers.( the second screenshot)
by sql query, we can see three actual frametimeline slices with same name's layer_name(the third screenshot)
we can't measure the actual frame timeline of launcher, because it's just the launcher background
how do you do in this situation(how to measure the launch aniamtion)?