• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why are my fetch/flush so slow???

F

frizzlefry

Golden Member
Seems I might be having some problems fetching and flushing my buffers.

It's a brand new system but something's goin on. I'm on a 384+ cable connection. Typical dl speeds are around 3000+mbits/sec. I'm guessing it's the dlink (crappy ass) network card I have on here. My other computer's gota linksys pci card and that one doesn't seem to have problems. Anyone ever experience painfully slow transfers to the distributed servers? I'm tlaking like 2-3 packets per second.

Help please.
 


<< Typical dl speeds are around 3000+mbits/sec >>



I HAD to address this first. &quot;Average&quot; T1 lines get about 150 KB/s or about 1.5Mb/s. A T3 gets about 45Mb/s. Somehow I have a hard time believing that you're getting the equivalent of about 67 T3 lines from a 384 Cable connection.

At any rate, the speed you are talking about isn't that unusual. Plus you have to realize that other people are also on that same Proxy server so you may not be the only person that it is handing blocks out to. 2-3 per second, if you are using 2^33 blocks is about 128-192 work units per second and that should fill up one machine plenty quick.

Joe
 
Oh my bad. Hehe. I meant to type 3mbits/sec I know it's faster than most. But that's what I get. Not many ppl around here use cable. Most jumped on the DSL bandwagon, which sadly IMHO was the wrong choice. Thanks for correcting on the numbers though.

😱
 
But it still doesn't explain why on my other older computer with linksys adapter, it send 200+ packets in a matter of seconds.

I think I'm gonna tear this dlink out and swap with my other and see what happens
 
It might very well be the network card, but it may also be one of two things. #1 is that Dnet's servers are in a round-robin, so the &quot;better&quot; machine may be getting a fast, emopty server all the time, while the opposite is true for our &quot;slow&quot; machine. The other is that the &quot;faster&quot; machine may use smaller packets, so it can transfer more in a sigle &quot;burst&quot;.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top