I'm just thinking about migration from xcache to eaccelerator because
the cache is quite useless on our FastCgi config with xcache, because
of shm...
So I configured a tmpfs disk-only cache, I verified that the cache
isn't resetted as it was before with xcache, so it's good, BUT it
seems there are cache for each process anyway, so if I configure a 4M
cache for eaccelerator, with 10 php-cgi processes for this vhost, the
cache on my tmpfs directory grows to 40M !!! Annoying !
Did I make something wrong ?
Question n°2 : what happens if the tmpfs partition become full ???
This is my php.ini :
extension="eaccelerator.so"
eaccelerator.shm_size="4"
eaccelerator.cache_dir="/tmpfs/eaccelerator/managergo"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="1"
eaccelerator.log_file=""
eaccelerator.keys = "none"
eaccelerator.sessions = "disk_only"
eaccelerator.content = "disk_only"
Thanks in advance !
Chris
the problem of this growing cache is really annoying, I can't use
eaccelerator in production if I can't solve it. Could anybody help
me ?
Regards,
Chris