I really hate to say it, but if you're going down this route, something else is wrong. Memcached's internal response times are never the problem.
Are you still working on that issue we discussed a while back? I got overbusy due to a conference but we should bring it up again. On Fri, 12 Jul 2013, Manish Jain wrote: > Nice. Is there any methodology I could apply to actually gather server side > response times, say even at the cost of slightly performance > degradation? > > > On Fri, Jul 12, 2013 at 3:47 PM, dormando <[email protected]> wrote: > On a healthy machine, over the network, and memcached isn't overloaded, > 0.1ms response times are what you should expect. > > On Fri, 12 Jul 2013, Manish Jain wrote: > > > Then, what would be a reasonable estimate of latency of GET and SET > operations on memcached server? A milli second? > > -mrjn > > > > > > > > On Fri, Jul 12, 2013 at 3:32 PM, dormando <[email protected]> wrote: > > Those don't really lag... just "stats sizes", so don't call > that one. Also > > "stats cachedump" isn't very fast. > > > > If there's any latency at all on a standard operation it's > almost always > > an outside issue (swap, network, etc), or a massive fault of > the software. > > > > Just adding timing measurements internally slows down the > entire operation > > significantly, which is why we don't do it. > > > > On Fri, 12 Jul 2013, Manish Jain wrote: > > > > > Is there a way to get server side latency stats for Memcached > operations, like GET, SET, INCREMENT etc? > > > memcached stats tells you total number of gets and sets, but > doesn't indicate anything about the latency of those operations. > > > > > > Cheers, > > > Manish > > > > > > -- > > > > > > --- > > > 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 [email protected]. > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > > > > > > > > > -- > > > > --- > > 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 [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > -- > > > > --- > > 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 [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > > > -- > > --- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > > --- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
