task #258
Caching mechanism
| Status: | New | Start date: | 05/11/2012 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 0.3 |
Description
We need caching for :
- queries that are issues very often, for filters construction for example (memcache)
- pages
Associated revisions
refs #258 basic caching, first step
cached files are dropped every time a new RPM is added or a RPM is
removed
refs #258 added cache on menu
History
Updated by Samuel Verschelde about 1 year ago
I added basic caching for parts of madb. Cache is cleared everytime there's a new package added to madb or a package removed.
Updated by Samuel Verschelde about 1 year ago
Some partials and components could not be cached because their URL is not discriminant enough. We have to work on this :
- filtering banner
- RPM lists
- menu
- getUrlAction
Also I haven't cached package/show because the subscription part depends on the user.
I haven't cached the footer because some parts of it might be dynamic in the future.