A very quick note on the sort of improvement we’re seeing with eAccelerator in place on our CWIS application. I ran these tests with ab (ApacheBench, version 1.3d) which may or may not be the right tool for this task.
Without eAccelerator caching, 30 requests:Â Requests per second: 0.61
With eAccelerator caching, 30 requests: Requests per second: 0.94
So, with eAccelerator we can boost performance of this complex application by about 34%. On the face of it, that doesn’t seem like a tremendous increase but then this application does a lot of MySQL work behind the scenes so opcode caching can only take us so far.
On a relatively simple page, (a single, lightweight MySQL query) we see much more dramatic improvement:
Without eAccelerator caching, 200 requests: 47 requests per second
With eAccelerator caching, 200 requests: 384 requests per second
Happily, getting this sort of boost will free up server cycles to help process our more weighty applications. 🙂