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
Hello!
Did you consider switching from apc_cache_info way to APC[U]Iterator on some commands like apcu:regexp:delete. Iterator would allow to significally descrease memory consumption, especially on servers with low php.memory_limit and large apc cache size.
For now (using 1.11.0 version with php 5.4.45) I can`t even clear cache by regexp if php.memory_limit = 128M and apc.shm_size = 1G because of size of apcu_cache_info's data.
And this logic still remain in 2.* versions as I see.
The text was updated successfully, but these errors were encountered:
It might be because APCIterator is extremely prone to crashing PHP with the version of apcu that ships with Ubuntu 14.04. I've tried for a long time to get them to update it but it doesn't seem to matter what anyone says: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1374892
Maybe detecting the apcu version and only using the memory intense method for the versions < 4.0.6 is in order?
Well, we probably could use some configurable logic in this case, I suppose. I don`t say - to do checking for version inside tool itself, I mean - to use config options for this.
Also - is this the only reason to not use Iterator at all?
Hello!
Did you consider switching from apc_cache_info way to APC[U]Iterator on some commands like
apcu:regexp:delete
. Iterator would allow to significally descrease memory consumption, especially on servers with low php.memory_limit and large apc cache size.For now (using 1.11.0 version with php 5.4.45) I can`t even clear cache by regexp if php.memory_limit = 128M and apc.shm_size = 1G because of size of apcu_cache_info's data.
And this logic still remain in 2.* versions as I see.
The text was updated successfully, but these errors were encountered: