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 noticed that unlike the File cache, there is no folder structure created for the files. Does this mean there may be an IO overhead when caching millions of key/value pairs?
The text was updated successfully, but these errors were encountered:
Uhm... what? This library works by creating files that the opcache engine can load into memory. Similar to other cache engines used in Symfony. These files look like this:
My concern is that they are all at a single folder level.
You're right. Though as you say, the files are loaded into memory. If you are dealing with millions of key/value pairs which won't all fit in available memory, there might be IO overhead to consider. I have never tested that, though. Creating subfolders might help, but I have very little time to work on any open source stuff at the moment.
I noticed that unlike the File cache, there is no folder structure created for the files. Does this mean there may be an IO overhead when caching millions of key/value pairs?
The text was updated successfully, but these errors were encountered: