Marcus,
Just to be sure, what follows from max_open_dbs that Jan was talking
about is that once you hit that limit, your memory usage should be
semi constant. Adjusting the memory usage due to databases would then
be semi-indirectly configurable via that parameter. As always, I would
urge you to c
Thanks for your answers, its frustrating to not have a generall idea.
Are there any tweaks for reduction of memory consumption, like setting gc
aggresiveness or something? Can the VM output it's memory status somehow?
On Tue, Jun 16, 2009 at 3:40 PM, Jan Lehnardt wrote:
>
> On 14 Jun 2009, at 23
On 14 Jun 2009, at 23:03, Marcus Persson Lindqvist wrote:
Greetings all!
In short - what factors are involved in memory consumtion for
couchdb for a
large (x * 1000+) number of databases? Any hints welcome.
Each database requires a file handle and at least one Erlang process to
be open an
On Sun, Jun 14, 2009 at 2:03 PM, Marcus Persson
Lindqvist wrote:
> Greetings all!
>
> In short - what factors are involved in memory consumtion for couchdb for a
> large (x * 1000+) number of databases? Any hints welcome.
>
>
>
> I've recently starting to dig couchdb alot and are using it as primar
Greetings all!
In short - what factors are involved in memory consumtion for couchdb for a
large (x * 1000+) number of databases? Any hints welcome.
I've recently starting to dig couchdb alot and are using it as primary
storage of a backend-type application to much success and relaxation. It
re
