The APC issues are somewhat APC specific in most cases, they often revolve around memory utilization issues and garbage collection. Some of the work-arounds involve ensuring APC always has extra memory to prevent fragmentation. When fragmentation goes about 35-40% clearing out the entire cache to prevent increase in fragmentation which in many cases can reduce stability.
Loading large number of files in parallel is another thing that frequently can negatively impact APC, doing pre-loading or staggering the loading process is the work-around that typically prevents issues. On Thu, Feb 28, 2013 at 2:16 PM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > >> If you are referring to APC as the stable cache, that unfortunately is >> not entirely correct, it is still relatively easy to crash APC unless >> some work-arounds are applied. I was speaking to a several people at >> the conference just yesterday and they were indicating frequent >> crashes with APC, the work-arounds appear to have solved their issues, >> but those are not exactly obvious. > > Do we have those ways and work-arounds recorded somewhere? It would be a > very good idea to have tests for O+ to ensure there are no problems in > these areas (or if there are, to fix them :). My experience suggests > opcode cache solutions often tend to have issues in the same areas, so I > think it'd be very useful. > > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
