APC Shared Memory Behaviour
| From: | Scott MacVicar | Date: | Tue, 06 Sep 2005 17:36:07 +0000 |
| Subject: | APC Shared Memory Behaviour | ||
| Groups: | php.pecl.dev | ||
| Request: | Send a blank email to pecl-dev+get-2871@lists.php.net to get a copy of this message | ||
Hi,
I've got a few questions about the shared memory and I think this is probably the most appropriate place to ask them.
How are the shared memory functions and file caching functions handled in APC?
We had been using eAccelerator for a while but finally had to drop support for it after we found a rather serious bug that would happen in the following situtation.
One 32mb segment allocated in shared memory
Insert some data from scripts into shared memory
Scripts get cached in shared memory
Update data from scripts in shared memory. (failure)
The failure would occur as all of the scripts had used up the remaining free allocated memory so updating would fail.
How does APC handle this situtation? Does it keep seperate caches for user stored shared memory and scripts? Or does a sort of global cleanup get run on scripts when memory gets full?
Thanks,
Scott