The latest commits document the new statistics counters. If there're other that might be interesting let me know.
Mainly to compare before/after you only really need to look at the hit ratio. If your dataset is large enough to push items through cache, this is where the improvements start. Otherwise uh... if it actually functions that's good to know an generally obvious to monitor (non-corrupt data, doesn't crash). On Thu, 8 Jan 2015, Ryan McCullagh wrote: > Hi, > > I'm going to be using your lru_rework branch on my development machines > starting tonight. > > I'm looking for some ways to "monitor" it? > > -----Original Message----- > From: memcached@googlegroups.com [mailto:memcached@googlegroups.com] On > Behalf Of dormando > Sent: Thursday, January 8, 2015 9:25 PM > To: memcached@googlegroups.com > Subject: Re: memory efficiency / LRU refactor branch > > Hi, > > https://github.com/memcached/memcached/pull/97 > > I've been poking at the TODO list since originally posting and fixed a number > of bugs. I'm taking some extra time to think about the slab rebalancer > situation and will be doing more testing than coding from now on. > > Hoping to get some of you folks involved in testing. I'll give it a good soak > before merging. Please and thanks! > > On Wed, 7 Jan 2015, dormando wrote: > > > Hey, > > > > To all three of you: Just run it anywhere you can (but not more than > > one machine, yet?), with the options prescribed in the PR. Ideally you > > have graphs of the hit ratio and maybe cache fullness and can compare > > before/after. > > > > And let me know if it hangs or crashes, obviously. If so a backtrace > > and/or coredump would be fantastic. > > > > On Thu, 8 Jan 2015, Zhiwei Chan wrote: > > > > > I will deploy it to one of our test environment on CentOS 5.8, for > > > a comparison test with the 1.4.21, although the workloads is not as > > > heavy as product environment. Tell me if any I could help. > > > > > > 2015-01-07 23:30 GMT+08:00 Eric McConville <erichasem...@gmail.com>: > > > Same here. Do you want any findings posted to the mailing list, or > > > the PU thread? > > > > > > On Wed, Jan 7, 2015 at 5:56 AM, Ryan McCullagh <m...@ryanmccullagh.com> > > > wrote: > > > I'm willing to help out in any way possible. What can I do? > > > > > > -----Original Message----- > > > From: memcached@googlegroups.com > > > [mailto:memcached@googlegroups.com] On > > > Behalf Of dormando > > > Sent: Wednesday, January 7, 2015 3:52 AM > > > To: memcached@googlegroups.com > > > Subject: memory efficiency / LRU refactor branch > > > > > > Yo, > > > > > > https://github.com/memcached/memcached/pull/97 > > > > > > Opening to a wider audience. I need some folks willing to poke at > > > it and see > > > if their workloads fair better or worse with respect to hit ratios. > > > > > > The rest of the work remaining on my end is more testing, and some > > > TODO's > > > noted in the PR. The remaining work is relatively small aside from > > > the page > > > mover idea. It hasn't been crashing or hanging in my testing so > > > far, but > > > that might still happen. > > > > > > I can't/won't merge this until I get some evidence that it's useful. > > > Hoping someone out there can lend a hand. I don't know what the > > > actual > > > impact would be, but for some workloads it could be large. Even for > > > folks > > > who have set all items to never expire, it could still potentially > > > improve > > > hit ratios by better protecting active items. > > > > > > It will work best if you at least have a mix of items with TTL's > > > that expire > > > in reasonable amounts of time. > > > > > > thanks, > > > -Dormando > > > > > > -- > > > > > > --- > > > 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/d/optout. > > > > > > > > > -- > > > > > > --- > > > 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/d/optout. > > > > > > > > > -- > > > > > > --- > > > 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/d/optout. > > > > > > > > -- > > --- > 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/d/optout. >
