awesome! Analytics are much needed for our content server pages.
-e On May 22, 2014, at 2:11 AM, Shane Tomlinson <[email protected]> wrote: > On 21/05/2014 21:21, Edwin Wong wrote: >> >> We have server monitoring of sync/FxAccounts response time but I found >> myself wanting more concrete numbers. There was also a bug on slow >> about:sync-tabs load time… >> >> So this happened: >> It runs https://github.com/edmoz/fxa-sync-client (uses zach’s library) to >> fetch sync data for a given account. It inserts the total time to fxa >> authenticate, fetch a token, then pull down the data into firebase db. Run >> that on jenkins every 15 min, then charts it with d3.js: >> >> http://people.mozilla.org/~ewong2/syncTabsPerf.html >> * note: that sync storage server assigns each account to a specific server >> node, so performance varies for each node. >> >> I’ll add bookmark fetch performance soon! >> >> -e >> _______________________________________________ >> Dev-fxacct mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/dev-fxacct >> > > Edwin, > I am in the process of adding front-end metrics to the fxa-content-server. > Navigation timing data [1] is being collected from browsers that support it, > so it should give us an insight into how long it is taking real users to see > the content server content. Now, if we could just get resource timing [2] > landed in Firefox, we could see how long individual resources take to load.. > > Follow the progress of the content server metrics PR at [3]. > > Shane > > ============== > > [1] - https://developer.mozilla.org/en-US/docs/Navigation_timing > [2] - https://bugzilla.mozilla.org/show_bug.cgi?id=1002855 > [3] - https://github.com/mozilla/fxa-content-server/pull/1146 > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
