in the way the keydir
> >> is stored, which could also potentially help with 1 (fewer
> >> allocations, etc). That, unfortunately, is not very likely to happen
> >> soon.
> >>
> >> So things will get better relatively soon, but there are some
> >>
fortunately, is not very likely to happen
>> soon.
>>
>> So things will get better relatively soon, but there are some
>> architectural limits that will be harder to address.
>>
>> On Mon, Aug 5, 2013 at 1:49 AM, Alexander Ilyin
>> wrote:
>> > Evan,
> architectural limits that will be harder to address.
>
> On Mon, Aug 5, 2013 at 1:49 AM, Alexander Ilyin
> wrote:
> > Evan,
> >
> > News about per key overhead of 91 bytes are quite frustrating. When we
> were
> > choosing a key value storage per key metadata size
s of
> items) so we were looking for the ways to reduce memory consumption.
> Here and here is stated a value of 40 bytes. 22 bytes in ram calculator
> seemed like a mistake because the following example obviously uses a value
> of 40.
>
> Anyway, thanks for your response.
>
&g
Evan,
News about per key overhead of 91 bytes are quite frustrating. When we were
choosing a key value storage per key metadata size was a crucial point for
us. We have a simple use case but a lot of data (hundreds of millions of
items) so we were looking for the ways to reduce memory consumption
d bugs against
the calculator, it's a bit wrong and has been that way for a while:
https://github.com/basho/basho_docs/issues/467
The numbers there look a bit closer to what you're seeing.
The good news is that I am looking into reducing memory consumption
this development cycle and ou
t;:"quorum","small_vclock":50,"w":"one","young_vclock":20}}
Disk usage is also about 1,5 times more than I have expected (270Gb instead
of 180Gb). I rechecked that I have n_val=2 (not 3), it seems alright. Why
this could happen?
Second question is about per
Hello Jacques,
It's A.
Cheers,
Nico
Am 30.05.2011 18:43, schrieb Jacques:
Hello,
I'm working on a riak deployment and have a question. I've read that
the approximate storage size per key is 40 bytes plus the size of the
key. Does the total storage size include the bucket name AND the item
Hello,
I'm working on a riak deployment and have a question. I've read that the
approximate storage size per key is 40 bytes plus the size of the key. Does
the total storage size include the bucket name AND the item key? If so,
I'll be sure to be prudent in my bucket naming.
E.g.
Key size: 15
