It should be mentioned that there is a huge bunch of various implementations of the statsd pattern; depending on ones existing infrastructure one may prefer one or the other. Heres a comprehensive list of them: http://www.joemiller.me/2011/09/21/list-of-statsd-server-imp...
I very much like the way in which metrics 2.0 enhances the duett of collectd and graphite ( http://metrics20.org/ ) See the amazing video how you can select across the data in the cluster of dieterbe's employer.
if you use collectd to feed values into graphite, you've got the advantage of its bulk writes. This article describes how its solved for rrd only collectd installations: https://collectd.org/wiki/index.php/Inside_the_RRDtool_plugi... but the effect also becomes visible if you use it to send values to graphite.
Its also good in reducing the amount of data you need to send to graphite.
How do you figure? Unless recent versions of Whisper have been totally rewritten, whisper writes each metric to a separate file. Submit hundreds of metric per vm/server every 10 seconds, and you get ridiculous amounts of tiny writes (e.g. 4 byte writes) fenced by redundant seek()'s and a number of other syscalls, no matter how much you batch up stuff before sending it to statsd.
Yes, compared to what IRC was in the 90'ies - definitely. In the age of DLS the then common ping floods aren't as effective anymore ;-)
While I'm idling about there in several channels like #citadel, it has become quiet there, and non technical channels seem to die out.
I guess IRC has to less XML inside to be hip or commercialy supported nowadays.
we'll see how long irssi keeps working ;-)
