On 05/23/2012 01:19 PM, Russell Beall wrote:
On May 23, 2012, at 9:36 AM, Rich Megginson wrote:
But based on what you say later in
the post, it's not unbounded, it's just not bounded by what
you set as the cache size?
Yes. I guess unbounded was the wrong word now that the ratio of
the boundary seems to be shown. The boundary of the memory
growth seems to be (6 * cachememsize).
It doesn't grow unless it gets hit with ldapmodify
operations.
Have you tried modrdn? delete? I was just wondering if the problem
is specific to ldapmodify.
It seems to correctly use the cachememsize and the
dbcachesize when reading in all entries and doesn't grow if just
hit with ldapsearch.
Ok, good to know.
Yes, please.
Ok.
Russ.
Thanks,
Russ.
==============================
Russell Beall
Programmer Analyst IV
Enterprise
Identity Management
University of Southern
California
==============================
On Apr 24, 2012, at 6:53 AM, Rich Megginson
wrote:
The thing in common is this - when the cache
usage hits the cache max size, you see unbounded
memory growth.
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
