Smarty

[gtraxx]

Hi,
I add the plugin Smarty_CacheResource_Apc.
I configured like this:

[U.Tews]

If you the APC cache resource the cache_dir folder of the file system is not used. The cache files are stored only in the memory area of APC.

NOTE: Even if you have APC installed but don't use it as cache resource you may see still speed improvements on compiled and cached Smarty templates because they are PHP files.

[gtraxx]

Thank you for your reply, I understand better how APC works
I'll also try memcached
_________________
* Creator of Magix CMS
* Creator of Magix cjQuery
* Co-maintainer jQuery UI Bootstrap

[adrik]

I did find this in the list of bugs for APC: http://pecl.php.net/bugs/bug.php?id=16736

But the long and short of it, it doesn't look like they are going to
change the way APC works.

"Sounds like with the inodes changing on every file update the cache
doesn't find the original entries in the cache (as they are key'd off
of
the inode #) and remove them on the new insert, so entries just stack
up.

Do you have a ttl set for your file cache? If not does setting one to
a
very low setting help? (entries will be removed if we come across them
or on a cache full scenario, rather than expunging the entire cache).

Another option here would be to upgrade to 3.1.1 or above, and use the
apc_delete_file($filename) before you delete the original file on
disk.