Hello Memcached users and developers,
I've analyzed Memcached implementation and suggested some improvements
here:
http://key-value-stories.blogspot.com/2015/02/memcached-internals-design.html
If I'm wrong in some details or conclusions, please correct me instead of
blaming, my only concern is
Yo,
On Mon, 16 Feb 2015, Roman Leventov wrote:
> Hello Memcached users and developers,
> I've analyzed Memcached implementation and suggested some improvements
> here:
> http://key-value-stories.blogspot.com/2015/02/memcached-internals-design.html
>
> If I'm wrong in some details or conclusions,
Hello Dormando, thanks for detailed and constructive reply.
On Tuesday, 17 February 2015 01:39:02 UTC+7, Dormando wrote:
> Yo,
>
> On Mon, 16 Feb 2015, Roman Leventov wrote:
>
> > Hello Memcached users and developers,
> > I've analyzed Memcached implementation and suggested some improvements
> Hello Dormando, thanks for detailed and constructive reply.
>
> On Tuesday, 17 February 2015 01:39:02 UTC+7, Dormando wrote:
> Yo,
>
> On Mon, 16 Feb 2015, Roman Leventov wrote:
>
> > Hello Memcached users and developers,
> > I've analyzed Memcached implementation and sug
On Tuesday, 17 February 2015 03:38:55 UTC+7, Dormando wrote:
>
>
> Again, in actual benchmarks I've not been able to prove them to be a
> problem. In one of the gist links I provided before I show an "all miss"
> case, which acquires/releases a bucket lock but does not have the overhead
> of pro
> On Tuesday, 17 February 2015 03:38:55 UTC+7, Dormando wrote:
>
> Again, in actual benchmarks I've not been able to prove them to be a
> problem. In one of the gist links I provided before I show an "all miss"
> case, which acquires/releases a bucket lock but does not have the
>
