So the connection is fast in terms of how much data it can transfer per unit time, but it is slow when you look at the response time. Because you can have a "bad connection" because you try to reach a server on the other side of the planet and you may have a "ping" of 150ms, but you can still have a huge bandwidth. Though this has to be broken up into two parts: bandwidth and round trip time. Of course speed is generally measured in "units per time" and we're interested in how many bytes can be transferred in a certain timeframe. I'm pretty sure more speed test websites would use a WebSocket connection to carry out the actual bandwidth test as well as the seperate ping / RTT measurement.įinally the term "speed" could mean different things. You should use the Stopwatch class for things like that. Next DateTime is not very accurate to measure very small time spans. SpeedTests deliberately sending out hundreds of MB if not GB to eliminate any potential slow down from establishing the connection. This is even more important when the actual data payload that you're loading is small. On top of that the request as well as response header contains significant amount of data that you did not consider. There are several handshakes involved before even a single byte of data is transferred. First of all as everybody should know, HTTP, especially HTTPS is notoriously slow when it comes to establishing a connection. There are several things wrong with your implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |