-
-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve layout cache efficiency by de-duplicating XML strings. #104
Improve layout cache efficiency by de-duplicating XML strings. #104
Conversation
I dus not sive info the code ... But how would this influence FPC cache extensions like lesti, mirasvit aheadworks amasty and others alike? |
@seansan If you have the layout cache enabled then it will significantly reduce the amount of cache storage used (and data written). That is all, but in cases where cache storage is valuable (such as in-memory caches like Redis, Memcache, etc.) it is quite important. |
From the code I think there can happen collisions if the same update with different handles is used |
It is the full XML that is hashed, not just a list so the only possibility for collision is in the sha1 space which I think is pretty reasonable. |
Merged 1.9.2.4 into 1.9.3.0 |
As announced a while back and made public first here: https://gist.github.com/colinmollenhour/14ed23d029e5b991a3e31ad1fe0841d4
I've been using this in production for months now with no issues. Massive cache storage savings.