Reduce ping?

[nomputer coob]

Are there any methods to reduce ping with the use of some time of software?
I'm using a dongle at the moment and the ping reaches 150 - sometimes 1000. :S

[Calum]

Using a wireless dongle, your ping will be high, it's the nature of those things.
To reduce your ping, go wired.

[nomputer coob]

sigh.   
bummer.
thanks

[Saurabhdua]

Can you please explain the nature of Ping?

I mean, are you trying to PING your DNS servers, some other website, default gateway..?

Changing DNS servers & using technology as encompassed within Opera's Browser does significantly reduces high ping times effect.


Choose Opera web browser, enable TURBO mode &...Zoom...your web-pages will render at a Ferrari speed!

[Thomas_Horscroft]

Ping is mainly identified in gaming, as i do alot of it. Going wired WILL NOT improve ping. Well it will, but buy 1-2Ms per 10 M of cable.(Go up) There is no way of improving your ping, unless you live closer to where the site/game is hosted.

Regards

[Calum]

Ping is mainly identified in gaming, as i do alot of it.

As well as anything else where networking is involved.

Going wired WILL NOT improve ping.

You sure?

Well it will

Ah.

but buy 1-2Ms per 10 M of cable.(Go up)

Huh?

Could you please clarify what you mean?  I can't seem to extract any sense from your posts.

[Thomas_Horscroft]

As well as anything else where networking is involved.
You sure?Ah.
Huh?

Could you please clarify what you mean?  I can't seem to extract any sense from your posts.

Callum, sorry still becoming used to this forum.

I ment, each 10 meter of cable used, you will loose 1-2Ms. Lowering your ping. Regards.

[Carbon Dudeoxide]

No....I don't think so....

[Thomas_Horscroft]

During my work expierience at the RAF in Kent, we tested it, this is the only way i know. Believe me the guys there know what their on about.

[Carbon Dudeoxide]

So if I ping Google's servers and receive a 42ms result, does that mean their server is ~420 meters away?

[Allan]

During my work expierience at the RAF in Kent, we tested it, this is the only way i know. Believe me the guys there know what their on about.

Give it a break. You're 15 - we're not impressed with your "work experience at the RAF...". Want to impress us? Start posting intelligent, correct information.

[Thomas_Horscroft]

Its not like that, and i was not trying to impress ANYONE its just ive been told by proper people

[Calum]

I'm still not following ...

[Carbon Dudeoxide]

Ditto....  You may experience ping issues if you're hooked up to your router with a 100m ethernet cable, but it wouldn't be a large impact.

[BC_Programmer]

During my work expierience at the RAF in Kent, we tested it, this is the only way i know. Believe me the guys there know what their on about.

you didn't test it very well. First, we're talking about a wireless dongle.

Second, the length of a cat5 cable has zero effect on ping time. I just did some tests myself.

Wifi:

Pinging www.l.google.com [74.125.53.103] with 32 bytes of data:
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=26ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=24ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=47ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=33ms TTL=55
Reply from 74.125.53.103: bytes=32 time=25ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=24ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=24ms TTL=55
Reply from 74.125.53.103: bytes=32 time=24ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=30ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=19ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55

Ping statistics for 74.125.53.103:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 47ms, Average = 23ms

Short wired ethernet (it's about 3 feet long):

Pinging www.l.google.com [74.125.53.105] with 32 bytes of data:
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55
Reply from 74.125.53.105: bytes=32 time=20ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55
Reply from 74.125.53.105: bytes=32 time=20ms TTL=55
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55
Reply from 74.125.53.105: bytes=32 time=20ms TTL=55
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=22ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55
Reply from 74.125.53.105: bytes=32 time=24ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=23ms TTL=55
Reply from 74.125.53.105: bytes=32 time=21ms TTL=55

Ping statistics for 74.125.53.105:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 24ms, Average = 22ms

and finally, a 25 foot ethernet cable I have for some reason:

Pinging www.l.google.com [74.125.53.103] with 32 bytes of data:
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=24ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55
Reply from 74.125.53.103: bytes=32 time=23ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=22ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=21ms TTL=55
Reply from 74.125.53.103: bytes=32 time=20ms TTL=55

Ping statistics for 74.125.53.103:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 24ms, Average = 21ms

the long cable has a lower average ping time then the short cable.

I wonder, if maybe this is perhaps related to the fact that the signals arrive at the speed of light? causing not only imperceptible "delays" based on cable length but entirely unmeasurable ones as well, likely in the area of yocto-seconds, if anything.

Preemptive:

"but that's the ping command, I'm talking about games"

Not much difference there. Ping time in a game is calculated by the delay between when the server sends out a packet to when the client receives it. clearly the actual connection (dial-up, DSL, Broadband) as well as the condition of the networks the packet has to pass through will have more impact then the length of a cord.