| commit | 8a2257965207cf117a33bc52dc9e39c94e35a343 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Wed Oct 09 18:04:39 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Wed Oct 23 22:14:34 2024 +0000 |
| tree | c5ff4af3782df27c7ec73a7e0be6024f61a4a8de | |
| parent | 35bd3d27b96af9bf77a0a1e69358b02550c063a5 [diff] |
Performance optimization for edit monitor Instead of log every edit event immediately when received the event, cache the events and log the cached events in batch periodically. In case when there are many edits events recieved in a short time (probably due to non-human operation like repo sync), send an aggregated edit event instead to prevent performance degrade. Test: atest edit_monitor_test Bug: 365617369 Change-Id: Ibe1613cf1e2eb37ebc5dfa5c029b990854fcf91e
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.