The schema contains "originCountry" that
should enable us to filter in
this way.
I have two points:
*Browser bias: *I was under the impression that Nav timing was only
available for modern browsers, so that might affect a bit of a bias into
the situation.
*Browser cache: *Browser cache is going to reduce any gains we might see
due to reduced latency or increased bandwidth. It would be nice if we
could compare the speed changes of cached/non-cached page/asset loading. I
don't think that the current schema will allow us to do this. Despite
this, we should still be able to get a good sense for how cached/non-cached
page loads were affected in general.
-Aaron
On Mon, Feb 10, 2014 at 9:43 AM, Dan Andreescu <dandreescu(a)wikimedia.org>wrote;wrote:
I was wondering if you have an easy way to
measure and plot the impact
in page
load time, perhaps using Navigation Timing data?
+10^9. I was rather excited to see ulsfo back up and I tried to quickly
figure some correlation out of
https://gdash.wikimedia.org/
dashboards/frontend/ , but I failed.
I think what's needed here is mostly some brilliant idea on how to
visualise / graph the data available there by region (and maybe also by
project / kind of editor e.g. unregistered vs. registered vs. sysop)
without making thousands graphs for each of the combinations. Or just one
graph for the region moved to ulsfo to start with of course. :)
Does the NavigationTiming data have the hostname of the varnish that
served the request, and do we have data on which hostname served which
geographic area at a particular time?
If so, we can generate a before and after average performance map by
region served, to see if there are any differences.
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics