I also wanted to note, that sync is a background task and something that just happens behind the scenes… Slower sync spikes may occur though users won’t notice unless they’re signing on the first time and checking on the sync state manually.
On May 21, 2014, at 1:21 PM, Edwin Wong <[email protected]> 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 _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
