Hi! I would usually stay out of things like this but could you please be less offensive? Saying things like this to someone that shared something nice to the public is beyond rude. This is clearly bad community spirit.
How would you feel if I (or the community) torched the new code that you're working on? Cheers, Toru On Wed, Apr 22, 2009 at 2:34 PM, gf <kak.serpom.po.yait...@gmail.com> wrote: > > Hi. Just it's dirty. So i'm writing good solution using libmemcached, > with daemon-mode that can report abnormal stats, with formatting > output.... Just wait :) 2-3 days. > > On 23 апр, 01:16, Mat Williams <williams....@gmail.com> wrote: >> hi, >> >> i like the idea for this project, nice work nicholas. i have looked at >> the output and it seems like it will be a useful tool for me too. >> >> gf, can you please tell me why this code is not good - should i be >> worried about running it against production servers? >> >> thanks, >> m...@. >> >> On Wed, 2009-04-22 at 13:00 -0700, gf wrote: >> > Hi. It's really good idea, but your code is not good, IMHO. >> > I've started the same project now.. >> > It will be released soon. >> >> > On 22 апр, 23:34, ntang <nicholast...@gmail.com> wrote: >> > > Hey all. First post... >> >> > > We've been using memcached for a while, but we've never really done >> > > much to monitor it past making sure the servers were up and running. >> > > Anyways, we recently had some issues that looked like they might have >> > > been related to memcached performance/ usage, and I figured it was >> > > about time that we started taking a look at it. We've added graphs >> > > for various stats so we can track them over time, and added nagios >> > > checks for the stats as well, but I also wanted a quick way to see the >> > > immediate state of the cluster. >> >> > > So I wrote a little tool. Hopefully people will find it useful. It's >> > > mostly configured by editing a config block up top, sue me. It's >> > > cheesy but works. The first time you run it, you'll need (at a >> > > minimum) to populate @servers. >> >> > > It's here:http://code.google.com/p/memcache-top/ >> >> > > (In retrospect I should've named it memcached-top, but such is life. >> > > I think people will be able to figure it out, and maybe if I put out >> > > another 'release' (*cough*) I'll rename it. ;) ) >> >> > > Thanks, >> > > Nicholas
