Cable connection, how much users can it handle?
Cable connection, how much users can it handle?
I want to setup a web server on my cable connection. It's 2mbps down and 320kbps up. I know the upload speed counts here, just woundering how many users could be on at once without seeing a tremendous slow down.
I put up a test page, http://24.226.196.100/test so you can see how fast it is, but of course there isn't anyone on it.
I put up a test page, http://24.226.196.100/test so you can see how fast it is, but of course there isn't anyone on it.
I'm running on that computer windows NT 4.0. I'm going to be upgrading it to a Athlong 600-700mhz with 256megs of ram. I'll run win2k on it to, the current computer is a p120mhz with 128megs of ram.
1-3 users huh, that's not much.
Do you know if you can stick two cable connections together? that would give me 80kb/sec. I don't think you can cus you would have two ips.
1-3 users huh, that's not much.
Do you know if you can stick two cable connections together? that would give me 80kb/sec. I don't think you can cus you would have two ips.
You need expensive hardware such as a Cisco router to successfuly bind two connections. Cheaper software solutions, such as those available from surfdoubler.com and midpoint.com, only allow limited load balancing and would not allow you to use both connections on a single process (eg. uploading or downloading a single file).Originally posted by jsbush:
Do you know if you can stick two cable connections together? that would give me 80kb/sec. I don't think you can cus you would have two ips.
[ 02-24-2001: Message edited by: glc1 ]
-
Kip Patterson
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
I don't know what your situation in Canada is, but in the US running a server on a cable modem is a violation of the terms of service.
Yesterday, it became a much more serious issue. We have a law called the Millenium Copyright Act, or something like that, which requires ISP's to police their users. With the legal status of Napster becoming clearer, the RIAA served notice on 20 major ISP's, including Time Warner, directing them to shut all the sites using Napigator. Gnutella and other similar techniques can't be far behind. My concern is that you may be putting a lot of effort into something that in the next six months or so will be absolutely banned.
With best regards,
Kip Patterson
Yesterday, it became a much more serious issue. We have a law called the Millenium Copyright Act, or something like that, which requires ISP's to police their users. With the legal status of Napster becoming clearer, the RIAA served notice on 20 major ISP's, including Time Warner, directing them to shut all the sites using Napigator. Gnutella and other similar techniques can't be far behind. My concern is that you may be putting a lot of effort into something that in the next six months or so will be absolutely banned.
With best regards,
Kip Patterson
Here's a tracert I did to your server. I couldn't ping you because of your firewall. 
Tracing route to 196-100.lr.cgocable.ca [24.226.196.100]
over a maximum of 30 hops:
1 41 ms <10 ms <10 ms 10.74.88.1
2 14 ms 27 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 13 ms 28 ms 14 ms 24.26.161.86
4 <10 ms 14 ms 27 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms 13 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 13 ms 14 ms 28 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 27 ms 14 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 13 ms 28 ms 55 ms 12.125.74.29
9 28 ms 68 ms 14 ms gbr6-p80.sl9mo.ip.att.net [12.123.24.238]
10 28 ms 27 ms 69 ms gbr4-p90.sl9mo.ip.att.net [12.122.5.190]
11 69 ms 27 ms 42 ms gbr3-p40.cgcil.ip.att.net [12.122.2.205]
12 27 ms 42 ms 27 ms gbr1-p100.cgcil.ip.att.net [12.122.1.154]
13 41 ms 97 ms 41 ms gr2-p340.cgcil.ip.att.net [12.123.5.130]
14 55 ms 55 ms 55 ms if-9-0-0.bb1.Chicago2.Teleglobe.net [207.45.193.13]
15 83 ms 109 ms 55 ms if-0-0.core1.Chicago3.Teleglobe.net [207.45.222.213]
16 83 ms 55 ms 55 ms if-8-1.core1.NewYork.Teleglobe.net [207.45.222.209]
17 69 ms 55 ms 68 ms if-7-2.core1.Montreal.Teleglobe.net [64.86.80.25]
18 68 ms 55 ms 69 ms if-9-0-0.bb4.Montreal.Teleglobe.net [207.45.221.170]
19 * * * Request timed out.
20 * * * Request timed out.
Tracing route to 196-100.lr.cgocable.ca [24.226.196.100]
over a maximum of 30 hops:
1 41 ms <10 ms <10 ms 10.74.88.1
2 14 ms 27 ms 14 ms msp-hub3-ubr-a-pos-1-0.mn.rr.com [24.26.161.81]
3 13 ms 28 ms 14 ms 24.26.161.86
4 <10 ms 14 ms 27 ms msp-hub1-gsr-a-pos1-1.mn.rr.com [24.26.161.9]
5 14 ms 14 ms 13 ms msp-mhe-gsr-a-pos5-0.mn.mediaone.net [24.26.161.65]
6 13 ms 14 ms 28 ms msp-mhe-gsr-b-pos-1-0.mn.mediaone.net [24.31.1.2]
7 27 ms 14 ms 27 ms nic-31-c2-030.mn.mediaone.net [24.31.2.30]
8 13 ms 28 ms 55 ms 12.125.74.29
9 28 ms 68 ms 14 ms gbr6-p80.sl9mo.ip.att.net [12.123.24.238]
10 28 ms 27 ms 69 ms gbr4-p90.sl9mo.ip.att.net [12.122.5.190]
11 69 ms 27 ms 42 ms gbr3-p40.cgcil.ip.att.net [12.122.2.205]
12 27 ms 42 ms 27 ms gbr1-p100.cgcil.ip.att.net [12.122.1.154]
13 41 ms 97 ms 41 ms gr2-p340.cgcil.ip.att.net [12.123.5.130]
14 55 ms 55 ms 55 ms if-9-0-0.bb1.Chicago2.Teleglobe.net [207.45.193.13]
15 83 ms 109 ms 55 ms if-0-0.core1.Chicago3.Teleglobe.net [207.45.222.213]
16 83 ms 55 ms 55 ms if-8-1.core1.NewYork.Teleglobe.net [207.45.222.209]
17 69 ms 55 ms 68 ms if-7-2.core1.Montreal.Teleglobe.net [64.86.80.25]
18 68 ms 55 ms 69 ms if-9-0-0.bb4.Montreal.Teleglobe.net [207.45.221.170]
19 * * * Request timed out.
20 * * * Request timed out.