I'm a little confused.

Pitbull

Verboten
Joined
Apr 8, 2006
Messages
64,432
Reaction score
5,088
Location
Hartbeespoort
Hi Guys

Pls read thru
http://mybroadband.co.za/vb/showthread.php?t=121459

Now I still stand by my understanding of latency, now either I have it completely wrong or what I have seen was true lies. I have seen slow damn connections give brilliant latency, and I have seen Brilliant speeds give crap latency. Maybe you guys know more and can help me understand what I know of Latency to be completely wrong :confused:
 
The way I see it:

Speed = DIAMETER of pipe (The bigger diameter the faster (volume) the water will come out)

Latency = Length of pipe (The longer the length, the longer you must wait for the water to start to come out at the other end of the pipe)

I think what V3G tried to say is that normally when you increase the speed, the latency will come down as well.

EDIT: Saying that speed is related to latency is incorrect. Look at latency on ADSL 384 and on 4096. It will be similar.

My 2c
 
Last edited:
Latency isn't only controlled by the length of the pipe, but by the number of blockages along its length. A poor pipe will have blockages that hold up the flow and increase latency.
Telkom, I'm looking at you.
 
I had 384 with a standars axxess account and got between 540 - 700 latency
Then i upgraded my line to a 4mb line and the latency stayed very much the same but was far more constant.
i then went unshaped and now on a 4mb line unshaped i get between 250 - 320.
280 being the average most of the time, and wonderfully playable.
line is with telkom (cant help that)
proveder is axxess.
 
I had 384 with a standars axxess account and got between 540 - 700 latency
Then i upgraded my line to a 4mb line and the latency stayed very much the same but was far more constant.
i then went unshaped and now on a 4mb line unshaped i get between 250 - 320.
280 being the average most of the time, and wonderfully playable.
line is with telkom (cant help that)
proveder is axxess.
 
I've got a Datapro uncapped, shapped 512mb over fibre at work and normally get around 235-600 on it. Sometimes it goes up dependet on whats nailing the network.

At home I have a 4mb unshapped Verizon account and normally get around 500-600 ms on it. During weekdays 08:00 -17:00 I get really crud latency and it will be anywhere between 235 and 2000ms. It's actually so poor I don't even bother trying wow on days off now.
 
I've got a Datapro uncapped, shapped 512mb over fibre at work and normally get around 235-600 on it. Sometimes it goes up dependet on whats nailing the network.

At home I have a 4mb unshapped Verizon account and normally get around 500-600 ms on it. During weekdays 08:00 -17:00 I get really crud latency and it will be anywhere between 235 and 2000ms. It's actually so poor I don't even bother trying wow on days off now.

Verizon is your problem, I get 400-600 on is semi-shaped fibre. on a 384k line
 
It also depends how it's routed. Telkom are renowned for routing most of their international traffic through hong kong first. Sometimes they feel like routing directly to New York etc.

Not sure how they decide when to route to where, but you can do a tracert to the servers to determine how many hops are in between you and the destination.

The less hops you go through the less your latency will be as well (hops = servers/gateways)
 
speed = how quick you can pull teh_warez

latency = the delayed action response time.

With high speed, you dont care if you click on a 200mb file and it only starts pulling 10seconds later, as long as it finishes the download in 1second you're smiling.

With latency, you can be on dialup, but if you click on "shoot" - you want the oke to drop then and there.
 
Speed and latency are not completely unrelated :p
At slow speed or low bandwidth data are break down into smaller packages and send in sequence thus giving bad (slow) latency. On the other hand with high speed connections data can be send as is without breaking into smaller packages thus the latency are faster.


For all those equations speed = distance / time
in PC terms speed seems to be data / time
Time in that equation is not related to latency

to conclude Latency is partially related to speed, but
speed is not related to latency :confused:
 
Let me try this one again:

Latency = how long it takes the cops to answer the phone
Speed = how fast they drive to your house.

high speed + low latency = 1st world countries.
high speed + high latency = cops in an M3, but 1st on a coffee break before responding to your call
low speed + low latency = Pofadder Moord & Roof department picks up your call in seconds and dashes out to the 1400 nissan champ bakkie to come to your rescue.
low speed + high latency = Eastern Cape police stations who answer your call after 2hrs, but currently have no vehicles to respond, so the only officer on duty must take the taxi.

So speed = the pace of the process once its under way
latency = how long it takes before said process is initiated after the request goes through.


I suppose the tortoise and the hare is also a good example:

Tortoise = low latency ... regardless of his top-end speed, he is off the mark immediately as the race starts
hare = high speed ... even if he sleeps the 1st 5mins of the race, his top end klaps it 6-love

now if the tortoise had high speed with its low latency, it would be cruisin' lekker ... similarly, if the hare had low latency, it would reach its top end much quicker- even though its the same top end speed.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X