![]() ![]() ![]() |
|
---------------------------------------------------------------
Nebukadnessar
richms: Friend gets 22megabytes a second on their steam store stuff on a 200/200 connection on the good desktop. Only gets 14 on the laptop. Cant blame the ISP for that.
michaelmurfy: A core i3 with 4gb of ram actually isnt that powerful - it is on the same scale in terms of power of my Chromebook which does have a lighter weight OS. Try a better laptop.
Also, since some speed test servers are only on gigabit connections themselves it is not a good guide on what you can get on your connection.
madmatt: Seems like a bit of misinformation going around here.
If you find your laptop isn't up to scratch, it's most likely because the NIC is passing packets to the CPU to handle, and getting the CPU to do the heavy lifting. Some onboard NICs do this, especially in laptops. You could watch out for this in Task Manager - check your CPU% as you run a speedtest for example. However you'd generally notice the laptop being sluggish if this was the case.
You mention that your laptop should be able to do better, and that other slower laptops do better than yours. Unless someone else has the exact same model laptop as you, with the same firmware revisions and hardware specs, and unless they are getting significantly better speeds than you with the same hardware, just discount that theory. There's any number of things about your laptop that might be causing issues - rule it out using the suggestions above and by other people - otherwise nobody can really help you.michaelmurfy: A core i3 with 4gb of ram actually isnt that powerful - it is on the same scale in terms of power of my Chromebook which does have a lighter weight OS. Try a better laptop.
Also, since some speed test servers are only on gigabit connections themselves it is not a good guide on what you can get on your connection.
It's not really about the 'i3' part as much as it is about the GHz and the generation of processor. It could be a really powerful processor, but without posting specs we're just guessing in the dark.
On your other point, do you have any sources to back that rumour up? I would be incredibly surprised if any of the Speedtest servers only run on a single non-bonded gigabit connection. For one, that's amateur-ish, especially given the increasing prevalence of gigabit connections, and secondly it's a terribly idea for Spark/Vodafone/whoever to do such a thing - it costs them next to nothing, especially compared to the hundreds of complaining customers they'd get if their speed test results were all terrible because the server could only theoretically handle one customer making a speed test at any one time. My guess is that those boxes have a minimum of 2x 10Gbit NICs, at a bare minimum.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
denemc: We only have one pc with a gigbit ethernet port so haven't been able to test with another machine.
It's interesting that it can get 450 up, but only 250 down, which sort of indicates it's not the PC slowing it down.
You should be doing an iperf test to another host - speedtest.net is flash player based and not very reliable.
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
Plus I am getting double up compared to what I am getting down indicates there is a problem.
Indicated a hardware issue to me
Is common to see that sort of thing when you run an ookla speedtest across a gigabit lan
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
VodafoneDylan:richms: Friend gets 22megabytes a second on their steam store stuff on a 200/200 connection on the good desktop. Only gets 14 on the laptop. Cant blame the ISP for that.
I find it fascinating how the bottleneck has shifted from the internet connection to the local network. It's quite amazing really, that rate of internet connection speed increase we've had.
Its interesting because I think sbibble has been saying that for years with regards to internal copper wiring.
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
Talkiet: I'm utterly convinced no-one here has a clue how ookla/speedtest.net actually work. The servers get by with WAY less connectivity than you might think because of the way the tests are conducted.
Our speedtest servers seem able to reliably test gigatown connections and I see many many results (from the server reporting) from people on many ISPs getting over 900Mbps.
IF we want to keep this on topic, then we'll wait for the testing of OPs machine at another connection, and the test of a known good machine at his connection.
Cheers - N
I used to run a speedtest.net node in Napier.
And yes like other smaller providers it was on a 1gbit connection. I took it down because it kept getting slammed by people from other countries such as india and random parts of asia.
So to run a speedtest.net node all you need is a 100mbit or higher connection.
The machine you run it on can be anything - ours was an intel NUC i3 with 2gb of ram and windows 7 pro.
Ookla provides some software which runs an http server on some random port, for windows or linux. It serves up jpg files of predefined sizes and resolutions. It might have speedtest500x500.jpg .... speedtest10000x10000.jpg
The jpg files are completely randomised pixels which makes it hard to compress.
The client
1) Starts by running an http GET for a 1kb text file on the server. This is how it times your pings. Its not actually a ping, its simply downloading a very small file. If the http server is under load, it may slow this down. You will probably get 5ms faster if you were to actually ping the server rather than just download the http files. But its a genius method when working within the restrictions of a flash player client.
2) The download test starts. It downloads a 100kb file and times how long that takes. You are about 10% through the speedtest by now.
3) Depending upon the time it took to download the 100kb file, it will start multiple downloads of larger jpg files, at the same time. Interesting factoid: If you are on a connection faster than 100mbits, your average speedtest consumes 1 gigabyte of data. Up at this level is where I notice your CPU and graphics capability will affect your result. Especially if the client is running via an RDP session.
4) The upload begins. The client generates random data and does an http post to the server this recieves the files and drops them from memory. The client times how long it takes to send the files, and it selects sizes based on your download speed.
5) An http post to ookla servers to report your statistics for their data mining goblins.
Also something interesting, here is my speedtest running in firefox on my dual core cpu - flash player can only access a single core of course, and you will notice that an 80mbit download uses approx 30% of the CPU core (no idea why) and the 90mbit upload uses approx 10% of the CPU core.
So thats just one reason why uploads can be faster than downloads.
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
|
![]() ![]() ![]() |