Confirmed users
96
edits
Necko/MobileCache: Difference between revisions
Jump to navigation
Jump to search
→Questions for guidance
Todesschaf (talk | contribs) |
Todesschaf (talk | contribs) |
||
| Line 69: | Line 69: | ||
These questions are intended to guide us in our goal of being able to turn on the disk cache (in some form) on mobile. This is not necessarily an exhaustive list, but it's a starting point so we don't necessarily go off the rails with ideas that may be more complex than we absolutely need. Bigger, better improvements to the cache as a whole can (and hopefully will!) come after mobile has anything at all. | These questions are intended to guide us in our goal of being able to turn on the disk cache (in some form) on mobile. This is not necessarily an exhaustive list, but it's a starting point so we don't necessarily go off the rails with ideas that may be more complex than we absolutely need. Bigger, better improvements to the cache as a whole can (and hopefully will!) come after mobile has anything at all. | ||
The questions that are <strike>in strikeout</strike> are no longer relevant. With a decent-sized cache, we no longer slow down Tp. This holds true on both internal and sdcard storage. There is, however, a difference in the win based on the filesystem (Samsung's RFS cuts our win by about 50% over other devices, though it's still a win). | |||
*What happens if we just turn on existing cache (now that all I/O is on separate thread)? | *What happens if we just turn on existing cache (now that all I/O is on separate thread)? | ||
**If this doesn’t slow down Tp, is there anything else preventing us from just turning it on and being done with the goal? | **If this doesn’t slow down Tp, is there anything else preventing us from just turning it on and being done with the goal? | ||
*How much space do we want the disk cache to grow to? | *How much space do we want the disk cache to grow to? | ||
<strike> | |||
*What is it that is making us slow down Tp? | *What is it that is making us slow down Tp? | ||
**Writing to cache? | **Writing to cache? | ||
| Line 96: | Line 99: | ||
****If so, why?! This should be mostly in-memory work! | ****If so, why?! This should be mostly in-memory work! | ||
*****Indicates that actual I/O is our problem, see above questions | *****Indicates that actual I/O is our problem, see above questions | ||
</strike> | |||
*Questions about certain things that may be needed to answer the above | *Questions about certain things that may be needed to answer the above | ||
**Is OS-level I/O single threaded? | **Is OS-level I/O single threaded? | ||
| Line 119: | Line 123: | ||
****Journaling? | ****Journaling? | ||
****Flush cache map on a timer and accept some inconsistencies from later page loads? | ****Flush cache map on a timer and accept some inconsistencies from later page loads? | ||
<strike> | |||
**What if the profile/cache is on sd card? | **What if the profile/cache is on sd card? | ||
***How often are we on sd card instead of internal storage? | ***How often are we on sd card instead of internal storage? | ||
| Line 125: | Line 130: | ||
***If we keep it enabled on sd card, what about security of cache data? | ***If we keep it enabled on sd card, what about security of cache data? | ||
***Can we keep cache on internal storage no matter what? | ***Can we keep cache on internal storage no matter what? | ||
</strike> | |||
**Have seen it’s a win on internal storage w/decent cache size (on a good fs) | **Have seen it’s a win on internal storage w/decent cache size (on a good fs) | ||
***Bug 645848 | ***Bug 645848 | ||