| commit | bfdd2461305ee48f603086b4204622c92aa670cf | [log] [tgz] |
|---|---|---|
| author | Akilesh Kailash <akailash@google.com> | Tue Dec 07 03:16:40 2021 +0000 |
| committer | Akilesh Kailash <akailash@google.com> | Tue Dec 07 20:38:29 2021 +0000 |
| tree | fb51ad2854c58463f59196ea2a4364fde6943369 | |
| parent | 0096a750c2c6885d591b7bd8aaebd382aafe9900 [diff] |
Enable userspace snapshots for OTA Bug: 202784018 Test: Full/Incremental OTA tested on CF, Pixel OTA Merge time performance on Pixel (bramble) ========================================================== Incremental - OTA - 389M OTA Operations: system - Copy-ops: 34060 Zero-ops: 678 Replace-ops: 93846 Xor-ops: 75490 product - Copy-ops: 241742 Zero-ops: 1970 Replace-ops: 292890 Xor-ops: 80763 vendor - Copy-ops: 110285 Zero-ops: 660 Replace-ops: 62163 Xor-ops: 23474 system_ext_b - Copy-ops: 44509 Zero-ops: 426 Replace-ops: 39475 Xor-ops: 44628 ==================================================================== 1: VAB - Compression with dm-snapshot (on Android S) Merge-time = 344 seconds (~5.7 minutes) 2: VAB - Compression with user-snapshot (on Android T) Merge-time = 53 seconds 3: VAB - Without compression (using kernel COW format) Merge-time = 33 seconds Compared to Android S, merge time improves by 84% with user-snapshots on Android T. The 20 seconds difference between (2) and (3) is because of two phase merge during compression which essentially serializes merge start time between partitions. On (3), there is no two phase merge as all the partition starts merge at the same time. When there is no two phase merge involved, (2) and (3) are nearly identical. ============================================================ Full OTA - 1.8G 1: VAB - Compression with dm-snapshot (on Android S) Merge-time = 40 seconds 2: VAB - Compression with user-snapshot (on Android T) Merge-time = 32 seconds 3: VAB - Without compression (using kernel COW format) Merge-time = 32 seconds =============================================================== Presubmit OTA testing enabled on Cuttlefish for ~1 Week with the feature enabled. https://v2-dot-atp.googleplex.com/tests/asit/ota/incremental_mixed_resume Signed-off-by: Akilesh Kailash <akailash@google.com> Change-Id: I88d15b94a48799996f38755063319269a3d70723
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.