![]() Based on this result, and appropriately sized chunck of randomly generated data is selected for upload.A small amount of random data is generated in the client and sent to the web server to estimate the connection speed.Because the test is shorter, the ramp-up period can take a significant part of the beginning of the test, leading us to drop another 20% of the bottom result slices. These factors lead us to drop the top 10% and bottom 10% of our slices as outliers.Īdditionally, we keep the default test length short for user experience. Since we are measuring data transported over HTTP (via Flash), there are the following factors that can affect speed: potential protocol overhead, buffering due to the many layers between our application and the raw data transfer, and throughput bursting due primarily to CPU usage. The remaining slices are averaged together to determine the final result.The fastest 10% and slowest 30% of the slices are then discarded.These samples are then aggregated into 20 slices (each being 5% of the samples). ![]() Throughput samples are received at up to 30 times per second.Once we start downloading, we use up to four HTTP threads to saturate your connection and get an accurate measurement.We prevent caches from throwing off results by appending random strings to each download.Our goal is to pick the right amount of data that you can download in 10 seconds, ensuring we get enough for an accurate result but not take too long. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |