simple question (maybe)

[JoeBloggs]

Hi Guys,

 

I don't understand this fully and can't seem to find the answer on google.

 

If I have a 10ms ping to our web server hosted online with our 100MB leased line, would increasing the bandwidth to say 200MB decrease the ms ping at all?

 

Or would it just download things quicker?

 

My thought was 1 packet is 1 packet so doesn't matter on bandwidth?

 

thanks

Edited January 12, 2017 by JoeBloggs

[mavhc]

In general it wouldn't change the ping, unless the line is fully used, then the ping reply would be in a queue with everything else. 10ms is really fast anyway

[Michael]

10ms is very fast I agree. You'd typically get 1ms on gigabit connections, but of course this will change as soon as it's being properly utilised.

[GuyJD]

It is my understanding that the ping time is the length of time it takes to route from your device to the server and back again, so it may improve slightly with a faster connection at your webserver end but it is only a single link in the chain if the other links in the connection are slower it will not get any faster.

[JoeBloggs]

thanks guys - that was just example.

 

We currently have our corporate database hosted in house - all our branches are on a private WAN via fibre so they all have 1ms response to the database server no matter where they are located geographically.

 

I'm being forced to get this put in a data centre for integration with our web site and I think we are getting a 15ms response time to the data centre. So my worry is the database everyone is using is going to get a lot slower. It's a huge database with massive tables etc.

 

So my thinking was if it is 15ms on a 100mb leased line if I double the bandwidth we may see some improvement on the ping?

 

thanks

[sparkeh]

Worth noting what ping actually does, which in this case is to report the latency between your machine and the web server. Unless the ping packet encounters congestion, the bandwidth won't effect the latency.

[RobD]

It all depends on upload and download between hops.

 

I.e. if you run a trace route to the location it should show how long each hop takes in MS.

[JoeBloggs]

thanks for answers guys although conflicting?

 

so ping is point a to point b and the time it takes........ but if i had giggabit bandwidth it would be 1ms ?

[Michael]

thanks guys - that was just example.

 

We currently have our corporate database hosted in house - all our branches are on a private WAN via fibre so they all have 1ms response to the database server no matter where they are located geographically.

 

I'm being forced to get this put in a data centre for integration with our web site and I think we are getting a 15ms response time to the data centre. So my worry is the database everyone is using is going to get a lot slower. It's a huge database with massive tables etc.

 

So my thinking was if it is 15ms on a 100mb leased line if I double the bandwidth we may see some improvement on the ping?

 

thanks

 

Forgive me for asking, but why couldn't you have allocated a public IP to your server hosting your database in house, then create a rule, so said IP can only communicate with your website's IP for security purposes?

 

You have to be careful as the 15ms response time may not be your connection. If their hosting provider is only using a 50Mb connection, the bottleneck is their end (if that makes sense)?

[Michael]

thanks for answers guys although conflicting?

 

so ping is point a to point b and the time it takes........ but if i had giggabit bandwidth it would be 1ms ?

 

A gigabit connection internally (on your LAN) should be 1ms, but a 1Gb WAN connection may not necessarily perform the same, as outside your network it's a completely different ball game!

[mavhc]

Ping is time to travel down all the wires from your computer to the server, plus time spent at each connector of said wires.

 

travel time is basically the speed of light, so unless you're going a long way, not an issue.

 

Time per connector depends on speed of connector, and how busy it is. If you're put a queue there's a delay. If the router deals with Gb links it's going to read and write your packets faster, plus probably have a shorter queue, and faster cpu.

 

Traceroute will find most of the routers between you and the server, and ping times for each

[JoeBloggs]

Forgive me for asking, but why couldn't you have allocated a public IP to your server hosting your database in house, then create a rule, so said IP can only communicate with your website's IP for security purposes?

 

You have to be careful as the 15ms response time may not be your connection. If their hosting provider is only using a 50Mb connection, the bottleneck is their end (if that makes sense)?

 

Yes I know... currently... "discussing"

 

The data centre would more than likely be rackspace

[sparkeh]

thanks for answers guys although conflicting?

 

so ping is point a to point b and the time it takes........ but if i had giggabit bandwidth it would be 1ms ?

 

Well...

Ok so, ping will tell you the time it takes to get from a to b, but this can be affected by a lot of things (the medium carrying the transmission, distance and congestion).

Bandwidth is how much data you can send down the pipe. So, if the line is not congested and holding the ping transmission up, you can keep increasing the bandwidth as much as you like but it won't make the ping transmission travel down the line any faster. If there is congestion that is slowing the ping down, then increasing the bandwidth will give you a lower ping.

 

Simple analogy, if you are driving on an empty motorway you can travel at 70mph, increasing the number of carriageways won't help you go faster. If there's too much traffic and you are all driving at 30mph, then doubling the number of carriageways might mean that you can all drive at 70 again.

 

Oh and bear in mind, that if you go for a connection with a lot of bandwidth, this might be delivered over different technology so the ping might actually be lower as the transmission can travel down the line faster (eg copper vs fibre)

 

Hope that makes some kind of sense.

Edited January 12, 2017 by sparkeh

[Michael]

Yes I know... currently... "discussing"

 

The data centre would more than likely be rackspace

 

Still makes no sense (depending on the application), as only a minimum of bandwidth would be needed to relay info to a website, whereas all your users are in house. I can only speculate as you haven't said what the database is for.

 

If the database needs to be accessed outside of school or it would help Staff work more efficiently, then yes I'm all for it. If it's something they'd never use outside of school, then there's little benefit in hosting in the cloud.

[JoeBloggs]

Still makes no sense (depending on the application), as only a minimum of bandwidth would be needed to relay info to a website, whereas all your users are in house. I can only speculate as you haven't said what the database is for.

 

If the database needs to be accessed outside of school or it would help Staff work more efficiently, then yes I'm all for it. If it's something they'd never use outside of school, then there's little benefit in hosting in the cloud.

 

Thanks Michael, I'm not in a School I'm in a private company!

 

- - - Updated - - -

 

Well...

Ok so, ping will tell you the time it takes to get from a to b, but this can be affected by a lot of things (the medium carrying the transmission, distance and congestion).

Bandwidth is how much data you can send down the pipe. So, if the line is not congested and holding the ping transmission up, you can keep increasing the bandwidth as much as you like but it won't make the ping transmission travel down the line any faster. If there is congestion that is slowing the ping down, then increasing the bandwidth will give you a lower ping.

 

Simple analogy, if you are driving on an empty motorway you can travel at 70mph, increasing the number of carriageways won't help you go faster. If there's too much traffic and you are all driving at 30mph, then doubling the number of carriageways might mean that you can all drive at 70 again.

 

Oh and bear in mind, that if you go for a connection with a lot of bandwidth, this might be delivered over different technology so the ping might actually be lower as the transmission can travel down the line faster (eg copper vs fibre)

 

Hope that makes some kind of sense.

 

Thanks this does clear it up a lot!

[Michael]

Thanks Michael, I'm not in a School I'm in a private company!

 

- - - Updated - - -

 

 

 

Thanks this does clear it up a lot!

 

Well same rule applies really - if the Staff you support would benefit accessing such a database outside of work, then it does make sense.

[mavhc]

Have two databases that sync

[Eek]

thanks for answers guys although conflicting?

 

so ping is point a to point b and the time it takes........ but if i had giggabit bandwidth it would be 1ms ?

 

Not quite, ping is the time taken from A to Z, not A to B. What may interest you is the response time from A-B, B-C, C-D, D-E etc.

 

Try these from your CMD prompt:

 

ping google.com

pathping google.com

tracert google.com

 

Compare the outputs and they will show you the response times per hop, between your PC, your nearest router, the next nearest link, etc. and would hopefully show you if there was a link in the chain that was much slower than the rest. That is the theory anyway, in your described situation this may not help much but hope this helps to explain.

[JoeBloggs]

I've spoken to Rackspace and we can actually get a virgin leased line fibre connection into the data centre so it will be an extension of our WAN and should be very low ms.

 

thanks all!