Geek Answers Handbook

Does PHP APC as a local object store have any limitations besides the size of the store?

I have been using PHP APC on production web service servers with a successful success of 10M / day for a long time.

I plan to upload much more data to the local APC cache.

In theory, it seems to me that since the APC call is mainly accessing local memory. It should not be a problem to call it 10,000 sec. / Sec. As far as I can tell, its limits can be in the amount of memory, but as long as the server has a free processor, it should not have problems with performance or corruption with high speed.

Is there any limit that I don’t know about, this may prevent me from using the cache object of the local APC object with very high speed on the application server (ubuntu).

Update: Apparently, according to the answers below, my question is not clear. I am not looking for alternative caching options (memcache, redis, etc.). My question is whether there are any problems or limitations when using local APCs at very high rates and reading concurrency.

+5
source share
1 answer

I am personally a big fan of using memcached for this type of storage. It has several advantages:

  • This is a program that focuses entirely on storage, and memcached development will always be focused on that. APC is primarily a cache for code that simply provides some access to user repository.
  • Apache ( -) APC . , memcached, , . , , Apache , , ( ).
  • , . , , , . memcached , APC - .

memcached APC, APC. APC, , .

+4

More articles:


All Articles