Taken from NASA's Site "It takes only about eight minutes for the Space Shuttle to accelerate to a speed of more than 17,000 miles (27,358 kilometers) per hour." I'm not sure of the exact speed of sound, but it's something like 650 MPH, so that would mean the Shuttle goes from 0-Mach 26.15 (Using 650 MPH, it can vary depending on air temp, but not by much) in 8 minutes.
You are correct in that T1's themselves do not use hubs, switchs, and are not ethernet. However, you are not taking into account what happens on the other end of the router once it's out of the provider's loving hands.
You can't just run the T1 into every device on a network, you either have to hub it (Cheap but SLOW) or switch it (More $, but better performance). Take my old High School for example: The district has a seriours cash problem (namely, no money) because we have no city government, they get no city taxes, and they get $0 corporate donations. So they chose to get a T1, but hub the hell out of it. In the English "Computer Lab" alone there were 2, 36 (I believe) port 3 Com hubs. This was the case all over the school, aside from our 1 router, every thing else was hubed, and this was also true for the whole district. As a result, the network worked fine at 6 AM when no one was there and everything was off, but by 10 AM, it dragged bad. It was so horrible that I was actually able to get faster bandwidth using a dial-up.
While I have no advice to find your T1's speed, I have a suggestion to improve it. Take the hub that you and the other two occupants share, sell it, and spend the money plus whatever else it takes to buy a switch. Hubs devide up the bandwidth, so you're probably getting around 1/3 the speed you could be getting, switches don't. They only forward data to the appropiate computer/network, where as a hub broadcasts it to every device on all connected networks barring a switch/router somewhere down the line. Add a switch and you will see a great improvment.
I think a lot of this has to do with the fact that kids today are brought up in a more technology oriented world. I, for example, was born back in 1982. My senior year in High School, I took a class in Cisco Computer Networking at the local community college (On my highschool's tab, of course). The thing I found was that our teacher, a very smart and very tech savy man in his own right, was getting outpaced by some of the students (Myself included) towards the end of the year. I think it really has to do with the age difference. He learned about the internet in the middle of his life while all the kids had grown up with it. While he was very good at what he did (He did have a CCNA), to us computers and the internet were basically second nature, we were raised on them and ever evolving technology. I still remember Gopher and original Hotline on my old Apple Performa (Still runs great). Anyway, by the last few months of the year, we were doing things with routers he didn't even know about, answering a few questions of his, and doing sick things with IP addresses by hand. I can still subnet a class A address in my head. I then got my CCNA a few months later without any other classes, and a few of my friends from Cisco got theirs not to long ago, but now the economy sucks, they can't get tech jobs, and I joined the Air Force, so in the end, a good time was had by all. Now what I'm interested in, is what the kids born today will be doing 15-20 years from now with technology and where my generation will be...
On the higher clockrate: This isn't necessarily a good thing. Anytime a jump is encountered in the code (i.e. GOTO), the processor, (and its lengthy pipe, something well over 20 stages last I checked, not sure about these newest Intel chips) is encounterd, all the instructions in the pipe need to be dumped and new code pulled, which = wasted clock cycles. I guess this means the processor can afford more wasted cycles. On the SPARC processors from the previous comment: Sun Micro's SPARC (Scalable Processor ARChitecture) is a 64 bit processor and in it's newest (that I'm aware) incarnation is 1.05 GHz with a 16 stage pipeline. The processor is scalable from 600 MHz to 1.5 GHz, which Sun anticipates expanding to at a later stage in development. Long and short, they're probably the best processor MHz for MHz. These things also rock for multi-processing. UltraSPARC III White paper.
Slashdot Mirror
Taken from NASA's Site "It takes only about eight minutes for the Space Shuttle to accelerate to a speed of more than 17,000 miles (27,358 kilometers) per hour." I'm not sure of the exact speed of sound, but it's something like 650 MPH, so that would mean the Shuttle goes from 0-Mach 26.15 (Using 650 MPH, it can vary depending on air temp, but not by much) in 8 minutes.
You are correct in that T1's themselves do not use hubs, switchs, and are not ethernet. However, you are not taking into account what happens on the other end of the router once it's out of the provider's loving hands.
You can't just run the T1 into every device on a network, you either have to hub it (Cheap but SLOW) or switch it (More $, but better performance). Take my old High School for example: The district has a seriours cash problem (namely, no money) because we have no city government, they get no city taxes, and they get $0 corporate donations. So they chose to get a T1, but hub the hell out of it. In the English "Computer Lab" alone there were 2, 36 (I believe) port 3 Com hubs. This was the case all over the school, aside from our 1 router, every thing else was hubed, and this was also true for the whole district. As a result, the network worked fine at 6 AM when no one was there and everything was off, but by 10 AM, it dragged bad. It was so horrible that I was actually able to get faster bandwidth using a dial-up.
While I have no advice to find your T1's speed, I have a suggestion to improve it. Take the hub that you and the other two occupants share, sell it, and spend the money plus whatever else it takes to buy a switch. Hubs devide up the bandwidth, so you're probably getting around 1/3 the speed you could be getting, switches don't. They only forward data to the appropiate computer/network, where as a hub broadcasts it to every device on all connected networks barring a switch/router somewhere down the line. Add a switch and you will see a great improvment.
I think a lot of this has to do with the fact that kids today are brought up in a more technology oriented world. I, for example, was born back in 1982. My senior year in High School, I took a class in Cisco Computer Networking at the local community college (On my highschool's tab, of course). The thing I found was that our teacher, a very smart and very tech savy man in his own right, was getting outpaced by some of the students (Myself included) towards the end of the year. I think it really has to do with the age difference. He learned about the internet in the middle of his life while all the kids had grown up with it. While he was very good at what he did (He did have a CCNA), to us computers and the internet were basically second nature, we were raised on them and ever evolving technology. I still remember Gopher and original Hotline on my old Apple Performa (Still runs great). Anyway, by the last few months of the year, we were doing things with routers he didn't even know about, answering a few questions of his, and doing sick things with IP addresses by hand. I can still subnet a class A address in my head. I then got my CCNA a few months later without any other classes, and a few of my friends from Cisco got theirs not to long ago, but now the economy sucks, they can't get tech jobs, and I joined the Air Force, so in the end, a good time was had by all. Now what I'm interested in, is what the kids born today will be doing 15-20 years from now with technology and where my generation will be...
On the higher clockrate: This isn't necessarily a good thing. Anytime a jump is encountered in the code (i.e. GOTO), the processor, (and its lengthy pipe, something well over 20 stages last I checked, not sure about these newest Intel chips) is encounterd, all the instructions in the pipe need to be dumped and new code pulled, which = wasted clock cycles. I guess this means the processor can afford more wasted cycles. On the SPARC processors from the previous comment: Sun Micro's SPARC (Scalable Processor ARChitecture) is a 64 bit processor and in it's newest (that I'm aware) incarnation is 1.05 GHz with a 16 stage pipeline. The processor is scalable from 600 MHz to 1.5 GHz, which Sun anticipates expanding to at a later stage in development. Long and short, they're probably the best processor MHz for MHz. These things also rock for multi-processing. UltraSPARC III White paper.