lucasgrinjander69 at gmail.com
Wed Oct 22 10:07:43 EDT 2014
Sorry, I don't know the MIME type I used. I use the python api with default
options. The doc says "string"?
2014-10-20 15:43 GMT+02:00 Luke Bakken <lbakken at basho.com>:
> Thanks for all the detailed information. This is not expected
> behavior. What MIME type are you using for storing the long integer
> data (64 binary bits, I assume)?
> I'd like to try and reproduce this. There have been issues with TTL
> and max_memory but they should have been fixed for Riak 2.0.
> Luke Bakken
> Engineer / CSE
> lbakken at basho.com
> On Mon, Oct 20, 2014 at 1:56 AM, Lucas Grijander
> <lucasgrinjander69 at gmail.com> wrote:
> > Hi Luke,
> > Indeed, when removed the thousands of requests, the memory is stabilized.
> > However the memory consumption is still very high:
> > riak-admin status |grep memory
> > memory_total : 18494760128
> > memory_processes : 145363184
> > memory_processes_used : 142886424
> > memory_system : 18349396944
> > memory_atom : 561761
> > memory_atom_used : 554496
> > memory_binary : 7108243240
> > memory_code : 13917820
> > memory_ets : 11200328880
> > I have test also with Riak 1.4.10 and the performance is the same.
> > Is it normal that the "memory_ets" has more than 10GB when we have a
> > "ring_size" of 16 and a max_memory_per_vnode = 250MB?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users