You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i don't know if it's the case for others, but in my case, most of the cache ends up in one file, while 2342 get created
this leads to a lot of I/O when using file based cache
there should be a way to have only one key being used. this would allow to load the cache from file only once, not having to make a cache hit for each single file
actually, i believe what is supposed to be lighter (one key per file to only change the files that have been changed) actually leads to a much heavier process when you could simply dump the whole array only once.
Description
Currently, there is one cache key per file as per
silverstripe-framework/src/Core/Manifest/ClassManifest.php
Line 588 in 2d472f4
i don't know if it's the case for others, but in my case, most of the cache ends up in one file, while 2342 get created
this leads to a lot of I/O when using file based cache
there should be a way to have only one key being used. this would allow to load the cache from file only once, not having to make a cache hit for each single file
actually, i believe what is supposed to be lighter (one key per file to only change the files that have been changed) actually leads to a much heavier process when you could simply dump the whole array only once.
Additional context or points of discussion
No response
Validations
The text was updated successfully, but these errors were encountered: