beat this speed,

cory 

beat this speed,

i'm faster in dl speed

i hve fiber internet in my house

Here's my ping to Chicago....

Noteworthy is that the pingtest is from your ISP to the test location, not necessarily from the server to the test.

1and1's servers are in Lenexa, KS, but apparently they're ISP is pinging from DC area. Here are my results on my dedicated server.

I would not recommend VPS unless it's somehow dedicated. I've read horror stories off other boards about surging demand redistribution, unanticipated shutdowns/restarts from others on the same blade......

I'm the only one on my server and I control as much as possible about when and if it shuts down.

Brings up an interesting ?....

Do any of you tech geeks know how to ping from the command prompt and get the performance metrics?

I know how to ping a server, but not how to get the elapsed time.....

Thanks Big Mike, I know that this is an old conversation, but I have had a few internet problems lately and I am wondering what other ppls experiences are. I use pingtest.net several times a day. I am using an inexpensive DSL and get 70ms ping and 1-5ms jitter to Chicago on a regular basis. On occssion, something happens out in the ether and my ping goes to 150 to 200ms and jitter goes to over 100ms and I start losing packets. That is when I stop trading, and if I notice a problem and am in a trade, I exit. It is really frustrating. I can usually tell when the internet is getting bad because my CPU useage starts peaking as the cpus are busy trying to keep the communications synchronized. Do others notice problems on occassion? If I go to a bigger cable, do the problems just go away, or is it inherant in the hops that the communication takes? Is there a way to force a path? tracert tells me that my path is from Arizona to LosAngeles to Dallas and then to Chicago. That is a lot of extra miles where I can pick up noise. Is there a way to prioritize Tucson to Chicago or at least to Dallas and then Chicago?

Any inputs are appreciated, and I am a huge fan of the site...Thanks for all that you do!!!!
Bob

Big Mike 

Speedtest.net is good for checking bandwidth. Bandwidth is important for a lot of things, but not really trading. Pingtest.net is good for checking latency. Latency is far more important than bandwidth in trading. Mike

Wireless or wired?

Mike

Tracert should also tell you where the latency is being added. For example if the hops through to your ISP are low latency, you can rule out something going wrong locally on your PC, or at the exchange/your ISP. If you notice large latency somewhere down the path there is really not much you can do about that. You cannot force a path, this is done via routing protocols (in this case BGP) inside the network core, automatically.

Set up a continuous ping (ping -t x.x.x.x) to an address at your ISP and to your LAN gateway (ipconfig /all will tell you your IP and your local gateway) and check if this also loses packets and latency rises while this problem occurs. This will tell you, as with the tracert above whether the problem is with your end or your connection to your ISP.

If this is not a local issue or an ISP issue, switching to a higher bandwidth connection will not necessarily help. It is possible with a different ISP you will have some different routing paths initially which may help, however once it gets further out of your ISPs network, chances are very high it will take the same path.

Hi RM, from the command prompt, use "tracert" to the address of interest... you can contact your broker and they will likely give you a test address to ping against...

Bob

RM99 

Brings up an interesting ?.... Do any of you tech geeks know how to ping from the command prompt and get the performance metrics? I know how to ping a server, but not how to get the elapsed time.....

Thanks Twiddle, I agree with all of your points and came to the same conclusions about faster internet with what I saw from tracert results. If this continues to be a problem too often, then I will have to upgrade the isp to minimize the issues as much as possible. I suppose that the only hope for us is that the isp's are spending money to increase capacity as more and more gadgets come on line.

Trade well and thanks for the response...
Bob

Twiddle 

Tracert should also tell you where the latency is being added. For example if the hops through to your ISP are low latency, you can rule out something going wrong locally on your PC, or at the exchange/your ISP. If you notice large latency somewhere down the path there is really not much you can do about that. You cannot force a path, this is done via routing protocols (in this case BGP) inside the network core, automatically. Set up a continuous ping (ping -t x.x.x.x) to an address at your ISP and to your LAN gateway (ipconfig /all will tell you your IP and your local gateway) and check if this also loses packets and latency rises while this problem occurs. This will tell you, as with the tracert above whether the problem is with your end or your connection to your ISP. If this is not a local issue or an ISP issue, switching to a higher bandwidth connection will not necessarily help. It is possible with a different ISP you will have some different routing paths initially which may help, however once it gets further out of your ISPs network, chances are very high it will take the same path.

Hi Big Mike...you are quick!!!! I need to learn how to see replies faster and how to respond faster. I am wired. Wireless gave me probs with the packet tests, so I just wired up.

Thx
Bob

Big Mike 

Wireless or wired? Mike