MyBB Community Forums

Full Version: MemCache, eAccelerator, files or DB
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
What one would be the fastest for mybb? like i have been told that eAccelerator is better but one says its not and i am so lost and with MYBB 1.4 having it i do not know what one i should use as i do not want to use the DB so what would you say.
For MemCache, eAccelerator or XCache, you need to actually have those extensions installed to use them.

If you don't, I'd stick to files.
To find out you make a page with phpinfo(); in it right?
Probably - try it and see for yourself.
Yup you can cool some thing we learn all the time :p

EDIT: okay so if you have them install what one would be the best as i know files would be if its not.
I have been using eaccelerator for years now with great success.
I, personally, prefer Memcache for caching, I use it for all my software that supports it.
Memcache is one I've seen utilized to a great extent. Smile
Personally, I'd go with it, but any would work better than files, imo.
I am reading about xcache...it appears to be very stable and faster the eaccelerator. I might give it a try on my new server.

http://neosmart.net/blog/2007/xcache-and...s-updated/

Still look into eaccelerator. It's awesome.

Quote: eAccelerator is a opcode cache for PHP. It increases
performance of PHP scripts by caching them in compiled state,
so that the overhead of compiling is almost completely eliminated.
Also it uses some optimizations for speed up of PHP scripts execution.
eAccelerator typically reduces server load and increases
the speed of your PHP code by 1-10 times.

eAccelerator contains PHP encoder and loader. You can encode any PHP
scripts with encoder to distribute them without sources. Encoded files
can be run on any site which runs PHP with eAccelerator. The sources
of encoded script can't be restored because they are stored in a compiled
form and the encoded version doesn't contain the source.
I've always used XCache myself.
Pages: 1 2 3