Best Opcache Operator, forum faster

[nothere]

Hi all. I was wondering, what is the fastest Opcache Operator option?. I am trying to test them, but I really don't understand what any of them do, or what to do when I pick them. The only one I understood was the Filecache because it says, "will store data directly on your hard drive in the directory ./vboptimise/filecache/. Please make sure the directory is writable." and still I don't understand it to well.

Can someone please explain to me what each option does, and how to get it to work? I looked in the HACK description and didn't find the answer I am looking for.

Thanks a lot.

[Neo_Angelo]

i think this is a job for @Deceptor to answer. from what i know, the other options you can choose from, some you may need to have certain things installed on your server (example xCache is one of them if i remember rightly) so in order to use some of the options you might need to either install the required things onto your server or use the filecache option which all servers "should" be able to use straight off the bat. Deceptor will better explain what each of the options do in greater detail.

[nothere]

Thanks, I will wait for this info.

[Deceptor]

Hi there,

All the options available are the major opcache systems available (with exception to Filecache), they will all store cache within RAM as opposed to the Disk (which Filecache does), obviously data read/write is a lot faster through RAM than the Disk. As for "Which is best?", on most setups your best bet is either XCache or Memcached - I prefer memcached due to its stability and scaleability. In terms of which will make the best improvement, there really isn't any if your using one of the systems supported other than Filecache, so whichever you have or get installed is fine.

You'll only need one installed, not really meant to have several systems to achieve the same thing installed. As for the specific differences in each operator, I'll list the generics but you can check their respective websites for more details:

- eAccelerator - Optimises PHP, has var caching (afaik var caching is still removed in the latest version, if they don't bring it back we'll be dropping support)
- XCache - Optimises PHP, has var caching
- Memcached - Var caching, extremely scaleable
- APC - Optimises PHP, has var caching, managed by the PHP dev team
- WinCache - Optimises PHP, has var caching, only available on IIS/Windows setups

Let me know if you have any further questions

[nothere]

TY so much. This has helped me a lot. Thanks again.

EDIT: SO to use 'memcached', what do I have to do after I choose it in the options?

[Deceptor]

Assuming memcached is installed, select the option then run a system test to make sure everything is working. If everything checks out, just enabled all the cache options, it Lite that'd be datastore/templates/styles, in Pro theres a dedicated section for cache settings with all that it offers, typically you'd just turn them all on

[SSSlippy]

Just a note most recommend using xcache on a single server. Memcache may be slightly faster but it requires an http request each time so until you have multiple front end servers xcache tends to be easier to run.

[Deceptor]

Just a note most recommend using xcache on a single server. Memcache may be slightly faster but it requires an http request each time so until you have multiple front end servers xcache tends to be easier to run.

Memcached runs through a local port (which isn't 80), no HTTP requests are required afaik. Do you have any details regarding this?

[SSSlippy]

Memcached runs through a local port (which isn't 80), no HTTP requests are required afaik. Do you have any details regarding this?

Sorry HTTP request was the wrong term used. It still has to make a request on that port compared to xcache which does not.