Necko/Cache/Plans: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 25: | Line 25: | ||
API design goes here. | API design goes here. | ||
== Locking | == Locking == | ||
Locking plans go here. Clearly detail what locks the cache will have, and strategies to avoid lock contention in performance-critical situations. | Locking plans go here. Clearly detail what locks the cache will have, and strategies to avoid lock contention in performance-critical situations. | ||
Revision as of 15:51, 11 March 2013
New Cache Plans
People
We have decided to rewrite the HTTP disk cache.
Design team:
- ?
Implementation team:
- ?
Design Requirements
- All APIs should be async.
- A crash should not invalidate the entire cache.
Performance Goals
- Primary performance target is mobile - Android and Firefox OS. On-disk layout must optimize for this.
- Make sure performance on spinning disks is good, but top performance here is not the priority.
API
API design goes here.
Locking
Locking plans go here. Clearly detail what locks the cache will have, and strategies to avoid lock contention in performance-critical situations.
On-Disk Layout
Clearly describe on-disk layout here.