4 ms·
Another way of gathering data would be a js-snippet that participating websites can include, which would run a random subset of the tests on some share of of vi
by sandstrom 12y ago
Another way of gathering data would be a js-snippet that participating websites can include, which would run a random subset of the tests on some share of of visitors, and report back to your service.
It'll be more realistic then DC -> DC queries.
- http://www.w3.org/TR/resource-timing/ http://www.w3.org/TR/resource-timing/
- http://googledevelopers.blogspot.se/2013/12/measuring-network-performance-with.html http://googledevelopers.blogspot.se/2013/12/measuring-networ...
- jimaek 12y agoIts realistic but not consistent and reliable. Like I said I want to test their raw performance without any variables in between. All providers get tested directly from the exact same locations and times. Thats the data I wanted to get. It makes it easy and fair to compare.
- acdha 12y ago> It'll be more realistic then DC -> DC queries. That depends on what you're trying to measure. If you want to know what the total end-user experience is like, Resource Timing is awesome. If you're trying to compare DNS providers without noise from the differences in client implementations and ISP competency, however, it'll be very noisy and you need a massive number of samples to avoid seeing trends which are really just sampling artifacts. The best approach would be to do both so you could compare the server response times with the measured client values so you can get an idea whether a slow-down this week is caused by something you have any control over.