Confirmed users, Bureaucrats and Sysops emeriti
1,680
edits
Necko/Cache/Plans: Difference between revisions
→Design Requirements
(→People) |
|||
| Line 21: | Line 21: | ||
* All APIs should be async. | * All APIs should be async. | ||
* A crash should not invalidate the entire cache. | * A crash should not invalidate the entire cache. | ||
* Don't over-optimize on-disk storage, use one file per entry to let OS optimize. | |||
* Support GZIP. Meta-data should say whether a file is gzip'd or not, can be turned on and off without causing corruption. Pass through files gzip'd from the network. | |||
* Version API for the cache so we can update easily. | |||
* Make use of fallocate. | |||
* Restrictive XPCOM API, start with just "clear cache." Require a use case to add to the API. | |||
== Performance Goals == | == Performance Goals == | ||