khttpd vs tux
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines
tux is more advanced than khttpd. It's also more intrusive to the kernel as far as core changes are concerned. These changes allow for higher performance, but you'll only notice that if you want to fill a gigabit line or more.....
Are there any good reasons why to run khttpd, then?
What I need is a server serving something between 50 and 500 concurrent clients - each downloading at 4-8Mbps.
Which one would be best? Anyone have an idea?
thanks
roy
---
Computers are like air conditioners.
They stop working when you open Windows.
Quoted 3 lines
Are there any good reasons why to run khttpd, then?
What I need is a server serving something between 50 and 500 concurrent clients - each downloading at 4-8Mbps.
Are those people doing tons of requests or are they just downloading large files? If they are downloading large files the type of serversoftware will be the least of your problems. About anything can give you the full bandwidth you can put out on your networkcards when you are serving few requests and are just pushing out mass amount of data.
When it comes to serving people such huge amount of data you should also take in mind that buying one big machine is not allways the right road to take.
As an example say that the data you're serving is less than 36GB in total. In that case you can easily buy 4 typical 2U rackmount servers with 9GB RAID1/36GB RAID1, Dual CPU, enough RAM, 1Gb NIC and pay less than a 8-Way system. Furthermore those 4 servers give you more redundancy (one can literally go up in smoke and you still lose only 25% power), they will in scale better and so on and so on.
In the end, unless you are handling tons of requests, your concern should be what hardware servers/switches/routers you need and certainly not what software. That discussion by itself would off course get quite off topic for lkml.
Dirk Moerenhout ///// System Administrator ///// Planet Internet NV
In article <[email protected]>,
Quoted 9 lines · Roy Sigurd Karlsbakk
Quoted 4 lines
tux is more advanced than khttpd. It's also more intrusive to the kernel as far as core changes are concerned. These changes allow for higher performance, but you'll only notice that if you want to fill a gigabit line or more.....
Are there any good reasons why to run khttpd, then?
What I need is a server serving something between 50 and 500 concurrent clients - each downloading at 4-8Mbps.
Which one would be best? Anyone have an idea?
Seriously? 500*8 Mbit/sec = 4 Gbit/sec
In that case you need at least 10 boxes, each with a gigabit card, with loadbalancing through DNS. Each box will do max. 400 mbit/sec and have 50 clients on it - standard apache will do fine, I think. Otherwise just add a few boxes.
You will need a Juniper M20 or a Cisco 124xx series with 2xSTM16 (OC64) or 1x10GigE upload capacity and 10xGigE slots in it. That will cost as much 100-200 of the Linux boxes so the Linux boxes are the least of your worries. Not to mention the cost of 4 Gbit/sec of Internet bandwidth.
Mike.
Signature · 2 lines
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" -- Albert Einstein.