Show HN: Bucky – Monitoring Client-side Performance

github.hubspot.com

27 points·zackbloom··7 comments

Boomerang.js is pretty much the best client side library capturing and beaconing back timing data.

How does Bucky differ from this?

What cleaning up of the data does it offer i.e. isn't not unusual to see quirks in the data that comes back from the Navigation Timing API?

There's already a pretty well known monitoring-related project called Bucky.

https://github.com/cloudant/bucky

OK, this looks awesome - I've been looking for a tool exactly like this for a while.

How does it compare with webapp analysers like NewRelic, for example?

I think the biggest difference is that it's open source and pushes data into the performance monitoring data stores many people already use (Graphite, OpenTSDB, etc.).

Would this add to load times on client end? Anyone know what kinda of delay do tools like these, NewRelic etc. add on the users browsing experience?

Effectively it won't change the load time at all. The javascript is less than 4kb minified, and the request is not made until several seconds after the last resource is loaded.

I can't speak for New Relic, but the overhead of this instrumentation would be measured in microseconds.

How many seconds is several - is there a danger that is might be long enough for the radio to have gone to sleep on a cellular connection?

Reply on news.ycombinator.com