| commit | f366a9b007909cc6d214fbee26a97e880734a094 | [log] [tgz] |
|---|---|---|
| author | Brad Fitzpatrick <bradfitz@android.com> | Tue Aug 24 16:14:07 2010 -0700 |
| committer | Brad Fitzpatrick <bradfitz@android.com> | Tue Aug 24 18:07:33 2010 -0700 |
| tree | 868fb57fd51d7c03ffbedb56ee27db5146e2c3b2 | |
| parent | e2978c8dcafdf20c2b49999ec423cb5f76d4a583 [diff] |
Negatively cache settings and proactively slurp settings into cache. The settings database cache is tiny (or should be tiny) and can be slurped into memory. Once it's in memory and we know we have it all we can avoid going to disk at all for keys not in the cache. This is a big percentage of the StrictMode violations & latency. Change-Id: I649411be0c40d348f58376ccfb3eda059fd69fbc