Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #9 on issue 157 by adam...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 Testing the water again If I were to strip out all the unnecessary library code from this patch it might only be about 500 lines of code, mostly in sflow.h and sflow.c with just a few macros in memcached.c. That would make it easier to vet/critique/improve -- and perhaps ultimately sign-off on? If there's an even chance then I'll do the work. Let me know. Neil -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #7 on issue 157 by rosso.gi...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 @Neil Thanks for your answer, we are using last version, 1.4.10 has problems with big slabs (we use 'em). So if you could just give as a patch or a full source for 1.4.13 I would be very glad. Thanks. PS Sorry for the personal post, but I didn't how to contact you directly.
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #8 on issue 157 by neil.mck...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 I pulled in the 1.4.13 changes (with no conflicts), and posted a download tarball on this page: https://github.com/sflow/memcached/downloads sFlow is enabled by default. So the steps are just: tar xvzf memcached-1.4.13-sflow.tar.gz cd memcached-1.4.13-sflow ./autogen.sh ./configure make make install memcached -u nobody It will pick up the config that is shared by hsflowd (via /etc/hsflowd.auto). http://host-sflow.sourceforge.net Please let me know how it goes: neil.mckee...@gmail.com Neil
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #5 on issue 157 by rosso.gi...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 Any news here? It would be very interesting to integrate official memcached with sflow. Thank you very much.
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #6 on issue 157 by neil.mck...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 FYI, there is a talk on this at Velocity tomorrow: http://velocityconf.com/velocity2012/public/schedule/detail/23487 If you would like to try memcached+sflow, please just let me know the particular version of memcached that you want to run, and I can make sure there is an corresponding build with the sFlow feature. It's not hard to add, and most users stick with the same version for a while, so I think it's quite sustainable to do it this way for now(?) Perhaps eventually the memcached experts will take it on, but in the mean time more users can only help. Neil
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #3 on issue 157 by s.schles...@ixolit.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 Hello Folks, is this patch going to be added any time soon? Regards, Stefan.
Re: Issue 157 in memcached: Instrumenting memcached with sFlow
Comment #4 on issue 157 by dsalli...@gmail.com: Instrumenting memcached with sFlow http://code.google.com/p/memcached/issues/detail?id=157 I really think this can exist as a plugin without having to modify the source tree. I'd rather not drop all of this in directly if it can be avoided.
