May 2014
12 Mon
13 Tue
14 Wed 10:00 AM – 06:30 PM IST
15 Thu 10:00 AM – 06:30 PM IST
16 Fri 09:30 AM – 10:30 PM IST
17 Sat 09:30 AM – 06:15 PM IST
18 Sun
Jemshad O K
Explains how to scale graphite/carbon from it’s default few thousand updates/min. to handle around 500K updates/min.
Collecting metrics and being able to represent them graphically in an efficient, scalable way is a key part in making your application clusters more robust in terms of both scale and performance. Graphite with it’s carbon backend is an excellent tool for such a purpose given the rich set of mathematical transformations that it supports on the underlying data. Though graphite as a frontend worked well, the carbon backend had it’s own limitations when coming to the data storing and retrieval part.
The session would cover little bit on graphite compared to other metrics collection and graphing solutions out there and then we move on to the specifics of using graphite at scale. We would go through various issues we faced, especially with it’s datastore, and how we solved them at InMobi.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}