Necko/Cache/Plans: Difference between revisions
Jump to navigation
Jump to search
(→People) |
|||
| Line 6: | Line 6: | ||
Design team: | Design team: | ||
* ? | * Michal Novotny? | ||
* Taras Glek? | |||
* Steve Workman? | |||
* Honza Bambas? | |||
* Jason Duell? | |||
* Vladan Djeric? | |||
Implementation team: | Implementation team: | ||
* ? | * Honza Bambas? | ||
* Steve Workman? | |||
== Design Requirements == | == Design Requirements == | ||
Revision as of 16:01, 11 March 2013
New Cache Plans
People
We have decided to rewrite the HTTP disk cache.
Design team:
- Michal Novotny?
- Taras Glek?
- Steve Workman?
- Honza Bambas?
- Jason Duell?
- Vladan Djeric?
Implementation team:
- Honza Bambas?
- Steve Workman?
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.