Comment #4 on issue 202 by [email protected]: TOP_KEYS feature fixes
http://code.google.com/p/memcached/issues/detail?id=202
Hi all,
Yes, I showed up for the hackathon but was too lazy to stay all night and
actually do the work :)
I guess I was hesitating because it wasn't clear if anyone was going to try
it. I didn't want to write an sFlow engine-shim just to commit it to the
void. If there is a real desire to see this problem solved, and there is
consensus that sFlow's "random-sampling with immediate forwarding" approach
is the best way to do it, then I'm happy to go ahead. It certainly seems
like there is now a clearer understanding of the need to do this without
impacting performance, so perhaps the time is right?
So to summarize, the questions are:
(1) "If I write this will you test it?" and
(2) "if it works great, will you bundle it with the default download?"
It may help to know that there are a number of freeware tools out there
that can receive and process sFlow in various ways, and there are also a
number of other sFlow agents that are also free and open-source. Here are
some examples:
http://ganglia.sourceforge.net
http://mod-sflow.googlecode.com
http://host-sflow.sourceforge.net
http://www.inmon.com/technology/sflowTools.php
(and of course there is also overwhelming support for this approach on the
network equipment side:
http://sflow.org/products/network.php)
Anticipating where this may lead, I think the big carrot is that down the
line you may find you can remove the top-keys code from the default engine
and clean up the critical path a little.
Thoughts?
Neil
