eAccelerator is a wonderful mechanism to speed up slow php. In general, the idea is simple 😆 when running php scripts, this nonsense keeps them up to date. opcode level and on the next call if there are no changes in the script the opcode copy is used. The result is faster execution at low server load, less waste of resources. Basically it is.
Now to share the simplicity that I managed to create. A little less than a week ago on a server I updated the php version I use because of the fatal one CVE-2010-4645 bug. I updated the version to 5.2.17 where I saw, that it has been repaired. I didn't risk it 5.3.5 version, that there are differences and I don't know how it will work , and most importantly, it was late at night. Said done. The update went more than smoothly, but after I finished I was impressed that the agility of the site dropped a lot. But one of the developers had warned me, that they would test new scripts and I didn't pay much attention to it. Yesterday I had to set some cron to php and when I played them I saw a rather unpleasant inscription, that my compilation of eAccelerator is for the start version of my php and does not work with the new one ;). Everything is clear now. I quickly recompiled the eAccelerator and everything fell into place according to rough observations. The loading of the pages dropped twice as valuable megabytes of RAM were released.. In general, at least I have already done the test and it is certainly useful especially for over 200 user online things become quite eloquent and at 400 😉 There are other mechanisms but according to the tests the eAccelerator is the most competent choice. I don't have much time for testing so I trust people 😀
http://www.youtube.com/watch?v = eJarZiMQaKA