bookkeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enrico Olivelli <eolive...@gmail.com>
Subject Re: Memory constraints on Bookie
Date Tue, 07 Mar 2017 07:42:26 GMT
Thank you Sijie, I will do some bench and profiling

-- Enrico

2017-03-07 3:20 GMT+01:00 Sijie Guo <sijie@apache.org>:

>
>
> On Tue, Feb 28, 2017 at 11:54 PM, Enrico Olivelli <eolivelli@gmail.com>
> wrote:
>
>> Hi,
>> I would like to put a limit on the amount of memory used by a Bookie.
>> The reason is that I am running the Bookie inside a JVM together with
>> other services and so it is quite important to be able to constraint the
>> usage of memory, especially OldGen and Direct Memory used by each component.
>>
>> From the docs about the configuration I see that the only relevant
>> parameters are related to the 'index'.
>> Maybe the ledgers GC can run into some memory spike ? Some long time of
>> big usage of heap.
>>
>
> Index and memtable size (if you are using sorted ledger storage) are the
> two main settings for tuning memory usage for bookie server.
>
>
>>
>> I am going to study deeply the code and do some profiling but I would
>> like to ask to the community if someone else as info about this topic.
>>
>> On the client side I think that only entries not yes fully processed
>> could be retained and maybe some minimal info about the topology of the
>> cluster. Am I right?
>>
>
> Yes, you are right. Only the pending entries and the network topology of
> the cluster are the minimal.
>
>
>>
>> Thanks
>> Enrico
>> --
>>
>>
>> -- Enrico Olivelli
>>
>
>

Mime
View raw message