Using webpagetest.org (a really useful tool and available to run on your own server), I generated a little app competition for a few of our Mozilla Foundation production apps.
Over the last few days, I’ve thrown a bunch of charts at you newly available from NewRelic.
We’ve been adding more and more apps with this capability, so here is some more fun data.
As my boss has noted, though, app server performance is not the same thing as user experience or browser performance.
Though we recently added monitoring of AWS resources in New Relic and now had information about load balancer utilization, RDS(Amazon Web Services database service) utilization, disk volume health, and even SES bounce rates, he was right…
We still had no idea how users actually experienced our applications.
My last DevOps gig got me used to having RUM(real user measurement), and I’ve been telling coworkers and boss “Soon, soon we’ll have browser performance data like these other languages”. While I’ve been telling them that, I’ve been experimenting with other solutions like Stackdriver, Pingdom RUM, bucky, and Google Analytics, despairing that node.js was a second class citizen in New Relic.
New Relic just announced v1.4.0 of its node.js agent, which finally includes browser performance. You can read about it here.
Today, we put this into production on webmaker.org
I have wondered how our location in Virginia (AWS datacenter) and lack of CDN impacted our international. After all, the webmaker team just spent a ton of effort localizing webmaker pages. Side note: We’re ranked in the top five or ten on transifex for localization projects. (HIGH FIVE AALI/TEAM)