| commit | a5dd6ac4865e26aa710388fbe030ec09cfbd96ac | [log] [tgz] |
|---|---|---|
| author | Rahul Ravikumar <[email protected]> | Mon Jan 27 14:51:32 2025 -0800 |
| committer | Rahul Ravikumar <[email protected]> | Wed Jan 29 16:52:58 2025 -0800 |
| tree | 4e61b3690217eebc155dad60bcb9f6bec88919ba | |
| parent | 3756026f44ce3abb4ddd0e31508b28fca62ff278 [diff] |
Multiplatform ready Tracing Driver
* Support emit perfetto traces on Android and JVM.
* `0` allocations when emitting a trace section.
* Use `mutableTypes` in Wire, and expose platform specific storage sinks.
* Coroutine based context propagation.
* Make it trivial to support other platforms (like Darwin).
1.5 ns 0 allocs TracingOverheadBenchmarkTest.reference
779 ns 0 allocs TracingOverheadBenchmarkTest.customTracingNoSink
3,523 ns 0 allocs TracingOverheadBenchmarkTest.platformTracing
11.0 ns 0 allocs TracingOverheadBenchmarkTest.customTracingDisabled
5,510 ns 2 allocs TracingOverheadBenchmarkTest.customTracingInMemorySink
There are five benchmarks.
* `reference` emits no trace sections (even when tracing is turned on.). This is just purely work.
* `platformTracing` = reference + emit trace sections using the `androidx.tracing` API.
* `customTracingNoSink` = reference + emit trace sections.
The trace packets go through their full lifecycle (including recycling).
The only thing we don't do is to encode the packets into the proto stream.
* `customTracingDisabled` emits no trace sections given tracing is disabled.
* `customTracingInMemorySink` = reference + actually encodes the packets into an in-memory proto stream.
Other Interesting observations:
* Note: Trace packet serialization costs are not fully accounted for in the `platformTracing` benchmark.
The actual serialization happens outside the perview of the benchmark.
* `NoOpSink` is unsurprisingly faster than the platform version (that emits trace sections).
* Tweaking the `bufferSize` on the Okio `Sink` does not make any difference to the benchmark.
Test: Added some JVM tests and tracing overhead benchmarks.
Relnote: Initial commit for Tracing Driver (experimental)
Change-Id: Iaeec406315fbc493339f8b2c1aabdd65c3875919
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.