Scaling Server Performance
An anonymous reader writes "When Ace's Hardware's article Hitchhiker's Guide to the Mainframe was posted on Slashdot, they got 590,000 hits and over 250,000 page requests during one day. This kind of traffic caused only a 21% average CPU load to their Java-based web server, which is powered by a single 550MHz UltraSparc-II CPU. In their newest article, Scaling Server Performance, Ace's Hardware explains how this was possible."
Now if they could use the same technology to create a web surfing client which generates that many hits with the same CPU load. Then you could put them together on the same network, and ....
they got 590,000 hits and over 250,000 page requests during one day. This kind of traffic caused only a 21% average CPU load ... they didn't respond to any of them.
Reliable, Great Value Hosting: $7.95/mo 2.4G/120G
Of course, it is incumbent upon all of us to rush out and try to the link to the article. And some of us to actually read it as opposed to just reading the title.
SLASHDOT THEM AGAIN!!!
I'm on it
seeing as it took Slashdot 35 seconds to serve me up this comments.pl?op-Reply page, yes, i think we are supposed to be impressed.
Cretin - a powerful and flexible CD reencoder
Can you say dry? 290,000 whatever, 21% something, 550 MHz, blah blah blah....
I'm not a computer, I'm a person. Give me graphs or don't bother.
Karma: Good (despite my invention of the Karma: sig)
>Garth Brooks covers this in his famous book "The Mythical Man Month" where he proves in a controled lab environment that Java under X86 runs on the order of Olog(n) slower than it does on a RISC chip like an UltraSparc.
WTF? Fred Brooks wrote this book, and I don't seem to remember RISC or UltraSparc chips, not to mention Java, in 1974. Garth Brooks is (AFAIK) a country music singer. Try again.
Sig for sale or rent. One previous user. Inquire within.
"The page cannot be displayed".
The lesson here is: put your money where your mouth is and you may end up eating it.
I prefer reading "The Mythical Man Month" in the original latin. Brooks' translation leaves much to be desired.
When I was benchmarking web servers in *1994*, servers could handle 100,000/hr, which is only about 30/sec.
But this is a Java-based server we're talking about.
NO CARRIER
I remember back in 1986 my Web-Enabled Elmo Daemon (WEED) was pretty lazy. But he sure could take hits. I think somewhere along the lines of 500 a day.
You're nothing; like me.
yeah but the blink tag was right around the corner! didn't over load server much, but ensured the clints had a swell time viewing.
Yes, but each one of those wizbang annoyances is just another hit to the server. dynamic generation of pages is the real server killer, depending on how much hoop-de-loop you're going through to make them.
;-)
Maybe it's just late, but I'm having a problem following all this technical jargon
Code, Hardware, stuff like that.