diff options
| author | Riddle Hsu <riddlehsu@google.com> | 2019-04-12 17:37:10 +0800 |
|---|---|---|
| committer | Riddle Hsu <riddlehsu@google.com> | 2019-04-12 17:37:10 +0800 |
| commit | 4e8e3b0204072a38026ce3955e77428e4dacb646 (patch) | |
| tree | 351c635af32d46593525f7b29e50c1e280086cb2 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 4f1adafc680df3c8d85b5467f5fa9921b7197346 (diff) | |
Reduce transactions for acquiring and releasing provider
App may access a provider frequently in a short time.
(Without using ContentProviderClient to keep the connection)
Then there will have some overhead for the management of
provider reference. So with a delay to release the provider,
the app can reuse the existing holder within the retain time.
Also change removeContentProvider to a one-way method to reduce
the time spent on app's main thread. This should be safe because
originally the app can acquire provider from any thread.
The cold start time of calendar app can be reduced by ~20ms.
Test: AppLaunchTest
Bug: 123043091
Change-Id: I220cec3deab18b658f4102f7eb9f47599c7c4b7c
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions