Re: Antw: [EXT] Re: dynlist vs memberof performance issues
>> Howard Chu <hyc(a)symas.com> schrieb am 23.05.2022 um
18:04 in Nachricht
<cc25e9ad-988c-fcd6-7bc0-0de6e3c530c7(a)symas.com>:
Ulrich Windl wrote:
>>>> "Paul B. Henson" <henson(a)acm.org> schrieb am 22.05.2022
um 04:51 in Nachricht
> <5d343067-aef3-b499-63e3-996f3d68051e(a)acm.org>:
>> On 5/11/2022 3:48 AM, Soisik Froger wrote:
>>
>>> Are this performance issues an expected side-effect of switching to
>>> dynlist - as the memberOf attributes are now dynamically calculated
>>> while the memberOf overlay used to writes these attributes - or
>>
>> I am also having ongoing sporadic issues with memberOf performance using
>> the new dynlist overlay. Initially, randomly a server would get into a
>> state where any query requesting the memberOf attribute would take in
>> excess of 30 seconds, whereas normally it would only take a fraction of
>> a second. The symptoms were the same, free memory, no swapping, but
>> insanely high read IO load.
>
> I'm wondering: If you'd make a core dump when the issue happens, how big
would such a core dump be with MDB?
> I'm afraid it would be insanely large, containing the whole database. Am I
wrong?
Yes, you are wrong.
mmap'd memory isn't included in core dumps by default.
OK, but that makes it hard to debug any MDB issues from the core dump unless significant
parts are copied in to private memory (which I think is not the idea behind MDB).
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/