eWeek Retest Shows 2.5-fold Apache Speedup 14
A reader writes "There's a retest story on ZD-Net about an upgraded Apache system.
Apache 1.3.19 running on a Red Hat Linux 7.1 system upgraded to the
2.4.5 kernel was able to process at peak throughput 4,602 Web requests
per second.
The last time eWEEK Labs did a big round of Web server benchmarking on
Linux was two years ago this month, when we did a retest of Linux and
Windows performance numbers as an audit of the Mindcraft Inc. tests.
"
Re:fp for 2 in a row! (Score:1)
I believe that the reversal of characters would constitute a grammatical error.
As such, your sig is forfeit, grammar nazi. I hope it was worth the pleasure - it's been a long run.
No comparison to NT (Score:4)
part of larger eWEEK story on Tux 2.0 / Linux 2.4 (Score:4)
Regards,
Tim Dyck
eWEEK Labs
Dying for Data of Interest (Score:2)
I would really be interested to see a full chart, showing static and dynamic web page performance of different OS+revision/httpserver+revision just so we can see what kind of progress has been made in this area over the past several years.
Yes, even entries with asterisks indicating heavy customization and tuning, like Ingo Molnar's tux server, would be interesting.
Probably, though, this is the kind of information that only gets into white papers that sell for $2500 apiece on tightly-controlled distribution.
now make HTTP caching proxies faster! (Score:1)
Re:Dying for Data of Interest (Score:2)
Yes, my death wish is the command of the IT news community, as this report [zdnet.com] about the blazing speed of Tux 2.0 appeared recently.
Re:No comparison to NT (Score:1)
Re:Dying for Data of Interest (Score:3)
Actually, one of the interesting points that they make in the article (taken straight from Ingo Molnar) is that much of the speedup in Apache is a result of inherited advantages from Tux. Many of the speedups that made Tux so fast have now been rolled into the mainstream kernel, so every application can take advantage of them. Molnar is quoted as saying that in the latest version of Tux, only 2% of the total time on the benchmark was spent in Tux-specific code, as opposed to over 50% in the original version.
You can say that this is an example of the real strength of Free Software. Tux served as a testing ground for a whole bunch of cool new technologies. When they showed how useful they are, Linus was able to roll them into the mainstream kernel. None of that would have been possible if Linus and Ingo hadn't been able to share their code.
Re:So after more than a year of tuning... (Score:2)
IIS has been improved also I'm sure. And IIS
probably has more development resources.
-Kevin
Lies, damned lies and benchmarks (Score:1)
useless comparisons (Score:3)
Most performance problems on real web sites come from dynamic page generation. And that performance is limited by choice of database, implementation language, and (most importantly) data model and distribution model among multiple servers. You can't make general comparisons there. At best, you can test your own application at a particular size on a variety of platforms and see which runs best. But even that comparison may be invalid tomorrow, after you made some changes to your system or your site has grown.
Re:No comparison to NT (Score:2)
Re:now make HTTP caching proxies faster! (Score:1)
As a squid developer the only thing I'm lacking is time. You'll find that the strides being made in apache are partially funded by people being paid to work on this. I can tell you that this isn't happening with squid. :-)
Tux 2.0 (Score:1)