-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support the timeline on Android release #47264
Comments
//cc @bkonyi |
For comparison, we do this on Fuchsia by defining SUPPORT_TIMELINE. |
Lines 113 to 116 in 8aa9716
|
This could potentially cause some perf regressions on Android, are we fine with that ? |
It'd be helpful to understand the cost (e.g. change in binary size, any runtime performance implication). I suspect the Golem benchmarks would catch these, and if not the devicelab right? |
Yes, not sure how to do devicelab runs on a local change, maybe we should make the change and monitor for perf regressions when it rolls into Flutter? |
SGTM. If it's not used it should be a pretty minimal cost, maybe one time if anything... |
https://dart-review.googlesource.com/c/sdk/+/214241 is being submitted and we should monitor it as it rolls into Flutter for regressions. |
Please see #47264 The Flutter team would like to turn this on in product mode for being able to systrace release applications. This change could have potential size and performance regressions and will be monitored as it rolls into Flutter. If the impact is not within acceptable ranges it can be rolled back. TEST=ci Change-Id: Iad6f9b831eaf60d15f03e368702fb25bc9ebc76c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/214241 Reviewed-by: Ryan Macnak <rmacnak@google.com> Reviewed-by: Dan Field <dnfield@google.com> Reviewed-by: Zach Anderson <zra@google.com> Commit-Queue: Siva Annamalai <asiva@google.com>
This is useful to systrace release mode applications on iOS. With this change and with systrace disabled, the `TimelineEventNopRecorder` is used so there should not be any performance impact. See also the following bug where this was done for Android. TEST=ci Bug: #47264 Change-Id: If3d127054d6345213fe0ade827dd60f7904a99a1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/289925 Reviewed-by: Ryan Macnak <rmacnak@google.com> Commit-Queue: Ryan Macnak <rmacnak@google.com> Auto-Submit: Jia Hao Goh <jiahaog@google.com>
Related:
#45143
flutter/flutter#90424
Systrace can be useful in release applications. Dart should support at least the systrace recorder in release mode.
It's not clear to me how much of an impact tracing has on performance though, and whether there are benchmarks that could show the cost of this even if it's turned off.
/cc @rmacnak-google @zanderso
The text was updated successfully, but these errors were encountered: