View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003381 | OXID eShop (all versions) | 4.05. Performance | public | 2011-11-21 10:06 | 2012-12-10 13:29 |
| Reporter | tjungcl | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | Past development | ||||
| Fixed in Version | 4.5.8 revision 42471 | ||||
| Summary | 0003381: new seo loadFromCache functionality currently wastes 99% hits | ||||
| Description | in rev 40049 there is a new promising caching mechanism for seo-table requests. However, the cachekey used for the filecache is the md5 of the viewid although the cachekeys of each entries are the md5s of the exact sql statement. Therefore you store identical sql-statement caches in filecaches that all have their own filename and so cant be shared. => istead of using viewid + "seo" as filename, use a common filename (only "seo" for example). The cache will still work correct, because it simply stores sql-statement-results, which do not depend on other factors that may influence the viewid. that way you get about 99% more cache hits :) | ||||
| Tags | Performance | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0003631 | resolved | Linas Kukulskis | existing seo-cache regularly overwritten with empty data |
|
|
we discussed this. to cache all links in one file can course some problems of file size, but there point to cache links by type something like that: article links per view; cms (content) links store in one file; category links also in another file. |
|
|
so now SEO cache is split and cached by type ('static', 'oxcategory', 'oxvendor', 'oxcontent', 'dynamic', 'oxmanufacturer'), except that 'oxarticle' type data is saved for each view - its not a good idea to cache product info in one file. |
