On Nov 27, 2011, at 2:32 AM, Siddharth Jagtiani wrote:
Is there tool that can manage/monitor memcached ?
There is an effort to instrument memcached with sFlow, which pushes out the
counters periodically and also takes random samples of the transactions
themselves. This way a collector
On Aug 18, 2011, at 10:48 PM, dormando wrote:
1) Sampling useful data out of a cluster.
2) Providing something useful for application developers
The second case is an OS X user who fires up memcached locally, writes
some rails code, then wonders what's going on under the hood. 1-in-1000
On Aug 18, 2011, at 5:19 PM, dormando wrote:
On a positive note, it does seem like there is some consensus on the
value of random-transaction-sampling here. But do we have agreement
that this feed should be made available for external consumption (i.e.
the whole cluster sends to one
On Aug 18, 2011, at 5:25 PM, dormando wrote:
Although there are already 30+ companies and open-source projects with
sFlow collectors I fully expect most memcached users will write their
own collection-and-analysis tools once they can get this data! Don't
you agree? So it's not about
On Aug 9, 2011, at 1:50 PM, Dustin wrote:
On Aug 8, 10:00 pm, neilmckee neil.mckee...@gmail.com wrote:
Well, all the memcached operations are built on top of it... do you
mean specifically multiget might call into the engine multiple times
for a single request?
Yes. That's one
I think it's clearer if we separate the requirements:
(A) continuous monitoring of the whole cluster, in production.
(B) troubleshooting a specific node, key, operation or client -- without
impacting (A)
For (A) you want the most robust, scale-out measurement you can find that will
not impact
I looked pretty hard at the shim idea back in May, but the engine protocol is
really a different protocol. There was not a 1:1 correspondence with the
standard memcached operations. If we define a standard sFlow-MEMCACHE
measurement then it should be something that any memcache daemon can
Hello all,
In adding support for the sFlow monitoring standard to the latest memcached
(see http://code.google.com/p/memcached/issues/detail?id=202) I used a scheme
for lock-free counter accumulation that might make sense for the memcached
stats counters too.
Background: the memcached
just don't think we should add a
complex solution to something that we don't notice ;-) )
Cheers,
Trond
On 24. mai 2011, at 21.31, Neil Mckee wrote:
Hello all,
In adding support for the sFlow monitoring standard to the latest memcached
(see http://code.google.com/p/memcached
