40Gbps Internet Connection

[Khamsin]

You're saying a 10k rpm hard drive couldn't write the data fast enough?

Generally it's not the HD's RPM that's the bottleneck. There's other things.

Is that why copying a 5 gig file takes me longer than 1 second?

[SephYuyX]

You're saying a 10k rpm hard drive couldn't write the data fast enough?

Generally it's not the HD's RPM that's the bottleneck. There's other things.

Is that why copying a 5 gig file takes me longer than 1 second?

Raptor HDs are one of the best commercial HDs with no better transfer speeds than 100MB/s, you either have a super de duper unreleased HD, have a raid setup of some 50 HDs transfering to another raid of 50 HDs on PCIe cards, or your copying a file to a different folder on the same drive. POIDH.


In any case, HD isnt the only bottleneck. The best case scenario you could get would be NIC > PCIe > HD (raid if have), but even then your 40GB/s NIC would hit PCIe and go down to 8GB/s and then down to 100MB/s (varies per setup). In most peoples setups it's, NIC > take a right turn > say hi to the ram > take a left turn > play with the cpu > wave to some more stuff > wire to HD > HD, brings it down to shit.


Im a bit rusty with my OSI or w/e stuff, so who knows what im talking about.

[evilbau]

You're saying a 10k rpm hard drive couldn't write the data fast enough?

Generally it's not the HD's RPM that's the bottleneck. There's other things.

Is that why copying a 5 gig file takes me longer than 1 second?

Raptor HDs are one of the best commercial HDs with no better transfer speeds than 100MB/s, you either have a super de duper unreleased HD, have a raid setup of some 50 HDs transfering to another raid of 50 HDs on PCIe cards, or your copying a file to a different folder on the same drive. POIDH.


In any case, HD isnt the only bottleneck. The best case scenario you could get would be NIC > PCIe > HD (raid if have), but even then your 40GB/s NIC would hit PCIe and go down to 8GB/s and then down to 100MB/s (varies per setup). In most peoples setups it's, NIC > take a right turn > say hi to the ram > take a left turn > play with the cpu > wave to some more stuff > wire to HD > HD, brings it down to shit.


Im a bit rusty with my OSI or w/e stuff, so who knows what im talking about.

I do, I had to write an OS in school, I don't know the details about how production OS's do it, it comes down to implementation but you are generally right about how data needs to move around and there are bottlenecks all over which wouldn't do 5GB/s.

[Cjskater]

Could this connection, crash a computer? lol

You make it sound like it would be using 100% of your computer up...thats why I ask. If so damn

[Charla]

Could this connection, crash a computer? lol

You make it sound like it would be using 100% of your computer up...thats why I ask. If so damn

A better analogy would be that of the connection sitting around with its thumb up a random personal orifice 99.98% of the time while it waited for the system to finish doing something else. Now, if most of the components had roughly equivalent bottlenecks (which is really really unlikely) it might be able to "use up" most of your computer, but that's not where crashes come from in the first place.

I can't even think of a situation in which a connection could be primarily responsible for crashing a single application, let alone the whole system.