View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006371 | OXID eShop (all versions) | 4.05. Performance | public | 2016-04-07 17:52 | 2022-02-01 14:12 |
| Reporter | keywan.ghadami | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Summary | 0006371: Varnish Cache-Invalidation is sent serialized | ||||
| Description | shop sends cache invalidations one after another, this can be optimized to send all at once. also all invalidations are going to the shop url, which might be a different system (e.g. https offloader) so it should be possible to configure the varnish IP Address for invalidations. | ||||
| Additional Information | in core/cache/connectors/oxreverseproxyconnector method invalidate | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
this has become a blocker for the project i am working on, because varnish could not handle all invalidation generated by shop when about 300.000 articles are updated via ERP Module. In the ESI Tuning module i added functionality to merge invalidations into 1 and revoved some invalidations not needed in the project. Also i removed the invalidation of the start page for articles, because at least in this project i can not see how an article update could influence the start page I plan to send a pull request soon. |
|
|
merge request is available at https://github.com/OXID-eSales/oxideshop_ee/pull/10 i tried to port things from the module written for 5.2.7, but i can not guarantee that things are compatible, please do not take it without exhaustive tests. |
|
|
This is not a blocker, but a very useful feature for users of varnish |
