RE: [PECL-DEV] APC timeout question?

> > If you look at apc_cache.c you will see that apc_cache_insert() calls > process_pending_removals() which looks like this: > Yes, I did have a peak, but wanted to make sure that I was reading it correctly. > > So yes, setting ap.gc_ttl will dictate how long stuff will > stick around on the deleted_list, but things only end up on > the deleted_list when they are actively removed through a > call to remove_slot(). This only happens when the same inode > gets a modified set of opcodes. > > So simply having scripts sitting around that don't get hit > often will not cause their cached opcodes to get timed out. > I agree with you that this would be a nice thing to have. > > -Rasmus > Rasmus, do you know of any plans for the next version, timeline, and/or new features going in? Features like the one I mention above, or others to help control the size of the cache memory as it is running would be helpful. On our primary server I can have the usage swing from 30-40 MB memory upwards of 70 MB in a 24 hour period of usage, when I examine some of the cached files there are a lot that are only used a few times a day and these just don't need to be cached in our implementation. Of course this is the humble opinion of a user... Best Regards, Shannon