Agreed - losing the opcode cache is what's killing you. For optimal performance, I'd recommend trying something like this: Varnish or squid (or ncache or...) in front of Apache (or other webserver) with Php (with apc, xcache, etc.) with Memcached in front of Mysql (or other db)
Varnish static pages and elements, use an opcode cache to cache php, use memcached to cache db calls, and voila. Fast(er) site. Nicholas -- sent via mobile device On Feb 28, 2010 8:53 AM, "Nicolai Scheer" <[email protected]> wrote: Hi! Am 28.02.2010 07:05, schrieb abchunter: > Hi, > > I have huge Vbulletin Forum and i am trying now memcached as i was > using Xcached before... So, you are not using xcache anymore? If so... > But i wonder why Memcached using so little memory and CPU. And does > not reduce the load much co... ... please note, that Xcache consists of two parts: An php opcode cacher and a key/value memory store (similar to memcached, except it is in-process). The memory store can be replaced with memcached, the opcode cacher not! So if you switched to memcached by disabling xcache entirely, you may experience, depending on your hit-rate, a huge load increase, because from now on, every php-script has to be compiled on each request. You should definitely use a php opcode cacher. If you use some kind of memory store in addition, the gain heavily depends on the way your application uses it. Greetings, Nico
