Testing your servers download and upload speeds the proper way:
By Andy A lot of people seem to have issues knowing the proper ways to test their servers speed, and complain when it goes wrong. There are lots of factors involved in getting the correct speed from your server. Bad speeds can be caused by any number of the following:
- Bad routing to/from the remote server
- Lack of capacity at the remote server
- Congestion on route to/from the remote server
- Not enough capacity on route to/from the remote server
- The remote servers general inability to supply the speed (high resource usage, high disk i/o, hardware problem)
- The local servers inability to take a fast speed (high resource usage, high disk i/o, hardware problem)
- The remote servers software not being good enough for a high speed connection
- The local servers software not being good enough for a high speed connection
Methods you shouldn’t rely on for speed testingSpeed tests like speedtest.net
You can use them, but don’t rely on them. Too many factors are involved and will often give you a very bad result. Factors from bad routing to not enough bandwidth on the remote server and silly things like flash lagging over remote desktop can all cause speed loss. Yes, it happens, and I’ve proven this one as well. 5Mbps with the browser maximised, 75Mbps with it minimised, guaranteed every time.
Torrents (unless they’re the ones specified below)
Torrents can be very, very sporadic in speed, however the ones listed below have plenty of seeds/peers, and they also have super seed boxes on them as well. This is the only time I will ever say a torrent can be used as a speed testing method, purely because I’ve tried these two torrents myself and achieved full speed every time with ease. No other torrents should be used if you want to use torrents as a speed test. Just don’t solely rely upon those results, do some other tests too.
Single thread downloads/uploads in any shape or form!
A single thread is rarely enough to give you the full speed of any 100Mbps box. If its local, like the OVH speed test, then sure, perhaps, but when it’s a remote file it will very rarely happen. It down to a lot of factors again, and its down to the TCP/IP protocol and all this rubbish which I won’t go into, as it baffles even me. Put simply, never rely on a single thread, always use two or more if you can. Don’t go mad though, you can overload your hard disk if you have too many running and slow your speed down that way. 2-4 threads should be plenty to max out 100Mbps from a good server without reducing performance on your own.
Here are some proper ways of getting a correct speed test for your server:-=========================================
I hope this guide has helped you understand the problems with speed tests and why it is so difficult to get an accurate reading. I also hope it helps you understand that 100Mbps is a lot of bandwidth to utilise. It’s not easy, and until you actually know you need such bandwidth, I wouldn’t worry about making sure you’re really getting it. Your server is supplied with it, and you can get it. It’s a case of several dozen factors that can stop it happening, all beyond OVH’s control.
=========================================
P.S: Could a MOD please sticky this? Please leave it unlocked so I can continue to update it. Thank you.