memory efficiency / LRU refactor branch

2015-01-07 Thread dormando
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

Re: How to store the key size more than 250 characters in memcached using java code?

2015-01-07 Thread Zhiwei Chan
In fact, it is almost impossible to meet a conflict. I think it is safe enough. see this link for more info: http://en.wikipedia.org/wiki/SHA-1 2015-01-07 14:11 GMT+08:00 sekhar mekala msekhar...@gmail.com: HI Ryan, Thanks for your valuable suggestion. But using md5 or sha1 to Hash your

RE: memory efficiency / LRU refactor branch

2015-01-07 Thread Ryan McCullagh
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

Re: memory efficiency / LRU refactor branch

2015-01-07 Thread dormando
To be extra clear; you can send feeback here or the PR. I don't care either way. 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

Re: memory efficiency / LRU refactor branch

2015-01-07 Thread dormando
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

Re: Issue 389 in memcached: internal clock drift from system time

2015-01-07 Thread memcached
Comment #4 on issue 389 by dorma...@rydia.net: internal clock drift from system time https://code.google.com/p/memcached/issues/detail?id=389 It could take a little while to get to it... you can see there're a lot of open bugs and pull requests :/ Sorry. -- You received this message

Re: memory efficiency / LRU refactor branch

2015-01-07 Thread Eric McConville
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

Re: memory efficiency / LRU refactor branch

2015-01-07 Thread Zhiwei Chan
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

Re: Issue 389 in memcached: internal clock drift from system time

2015-01-07 Thread memcached
Comment #2 on issue 389 by chr.eg...@gmail.com: internal clock drift from system time https://code.google.com/p/memcached/issues/detail?id=389 Hmm, doesn't quite sound that a fix will make it into one of the next releases :( Also I'm not sure if smooth correction can even be sanely

Re: Issue 389 in memcached: internal clock drift from system time

2015-01-07 Thread memcached
Comment #3 on issue 389 by chr.eg...@gmail.com: internal clock drift from system time https://code.google.com/p/memcached/issues/detail?id=389 - spew out an error message if there's a big difference (say 30s?) EDIT: A warning message would be better, i.e. let the internal counter jump