|
APC (Alternative PHP Caching http://us.php.net/manual/en/book.apc.php) is a memory based opcode caching system which supports variable caching inside of php scripts. It's among 3 major opcode cachers for PHP (the other two are XCache and EAccelerator). While APC sounds great (after all, to install it all you need to type is `pecl install apc`), it suffers from a few major flaws. My personal feeling, is that these flaws warrant its removal from PECL. Read more to see why APC sucks so bad... |
|
Read more...
|
|
|
In this first webcast, we explore why mod_php kills performance, and why fastCGI is better. Click readmore to see the video.
|
|
Read more...
|
|
|
Well, I was pointed to an article recently, http://reinholdweber.com/?p=3 , which lists 40 tips for php performance. I decided to put some of those to the test. Then, I started looking at some other of the common ways to do very common functions. Here's the results of the tests. All of these tests were done by measuring either 100,000 loops of each function, or 1,000 loops (for the longer running functions). By all means, don't take my word for it. Try it your self!
|
|
Read more...
|
|
|
One highly debated issue, and frequently asked question that I see, is "Should I install an OPCode cacher?" It's common knowledge that OPCode cachers can speed up complex applications significantly. What's debated, is the best one to use and what the difference is between them. So, that's what this benchmark session is for. To tell the difference between the OPCode Caches.
|
|
Read more...
|
|
|
Well, I've often been asked a number of questions about PageCache. Some of them include questions such as "How much does it help?", "What's the best storage method?", and "Which is faster, 2.0 or 1.0?". Well, I've put those questions to the test. In this latest round of benchmarks, I test PageCache with Joomla 1.0.14...
|
|
Read more...
|
|
|
<< Start < Prev 1 2 3 4 5 6 Next > End >>
|
| Results 1 - 5 of 26 |