|
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...
|
|
|
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...
|
|
|
Well, I've always highly recomended the Website Optimizer to people looking to determine what the problem with their website is. The only two things I didn't like about it, were the over exadurated download times, and no clues as to the health of the webserver in question. So, I decided to write my own. It may be a bit buggy at first, but bear with me. It not only gives you the real time data on how long it took this server to grab the page, it also gives you information on how long your server took to generate the request, how long it took to resolve the domain name, how long it took to connect, and how fast the download actually went... It also keeps track of the fastest pages and servers it connects to... Be sure to check it out (Performance Grader under Tools), or click here for the Performance Grader!
Discuss this article on the forums. (9 posts) |
|
|
In this third installment of the All About Speed series, I'm going to discuss the effect of HTML on speed. Now, I know most of you are thinking how much effect does HTML have on load times. A LOT. We have already looked at the time it takes for content to be generated, and the time it takes for it to reach the end users computer, but what about the time it takes to render? A poorly formated HTML file can take SECONDS to load in a browser (if not more). Sure, it may display how you want it to, but what does that matter if the user has already gotten bored and gone to another page? |
|
Read more...
|
|
|
In the second installment of this multi part series, I am going to talk about another extremely important topic when it comes to website performance. As you can probably infer from the title, that topic is generation time. Notice I said generation time, and not load time. There is a VERY important difference between them. Load time is the time it takes from when a user makes a request until the page is completely loaded (including all associated graphics and rendering). Generation time (by my definition) is the time from when the server receives the request, until the first useful piece of content is sent. |
|
Read more...
|
|
|
<< Start < Prev 1 2 Next > End >>
|
| Results 1 - 5 of 8 |
