----- Original Message -----
> On 06/05/2012 05:55 PM, Richard Megginson wrote:
> > ----- Original Message -----
> >> On Mon, April 23, 2012 20:38, Rich Megginson wrote:
> >>> Ok. The current theory is that the memory growth is caused by
> >>> the
> >>> churn
> >>> of entries being added to and removed from the entry cache. It's
> >>> not yet known why this growth is
> >>> seen. It could be just that the memory is getting fragmented, or
> >>> there is a real yet undetected
> >>> memory leak. That's why entry cache sizing and monitoring is very
> >>> important, to see
> >>> if you are churning entries in/out of the cache, and if that is
> >>> correlated with the memory growth.
> >> This memory issue is still occuring in the production environment
> >> after increasing the max entry
> >> cache size to 256MB, and it is impacting performance. See below
> >> for
> >> an output of the memory usage
> >> and the current size and hitratio of the cache on the 3 production
> >> IPA servers.
> >> How do you suggest moving forward to troubleshoot this issue?
> > Are you seeing https://fedorahosted.org/389/ticket/386 ?
> I don't think so. The cache numbers described in this ticket is much
> higher than my cache numbers.
> I've set the maxentrycachesize to 256MB, and each IPA server has 8GB
> memory. There should not have been a consumption of more than 1,8GB
> the 7 * cachememsize as described in the ticket.
> Beside I don't know where the heavy modify levels would come from.
> 100 new users we're moved to IPA last week, all having their
> changed, the accounts themselves already existed. But is that
> a heavy LDAP modify level?
I don't think it matters whether or not the modify level is heavy. If there is
a memory leak, a heavy modify level will make it more apparent more quickly.
> There seem to be a memory leak somewhere. How would you recommend
If you think this leak is a completely different issue than ticket 386, please
open another ticket.
Freeipa-users mailing list