[Date Prev][Date Next]
Re: Performance degredation between 2.4.39 and 2.4.44
- To: Quanah Gibson-Mount <firstname.lastname@example.org>, email@example.com
- Subject: Re: Performance degredation between 2.4.39 and 2.4.44
- From: Howard Chu <firstname.lastname@example.org>
- Date: Tue, 15 Mar 2016 12:31:05 +0000
- In-reply-to: <8CF87495A25A27D632D59B81@[192.168.1.9]>
- References: <07526F16C93E2796ABFFC689@[192.168.1.9]> <D45E3ABAD376073B255ED306@[192.168.1.9]> <70785EFC09283852629738A3@[192.168.1.9]> <56E3F03B.email@example.com> <8CF87495A25A27D632D59B81@[192.168.1.9]>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 SeaMonkey/2.42a1
Quanah Gibson-Mount wrote:
--On Saturday, March 12, 2016 10:32 AM +0000 Howard Chu <firstname.lastname@example.org> wrote:
So apparently, you want the ration to be no more than 30:1, otherwise
perfomance degrades substantially.
On a 1M entry database I see no performance difference between using the
default rtxnsize (10000) and setting it to zero. Verified using both head
I see the differences I've noted with at least 3 different DBs of varying size
now. I've dropped the 300kish one on ada.
With your 300k entry DB and config I see a full subtree search take about
10.4s with rtxnsize = 0, vs 11.7s with rtxnsize = 10000. Measurable certainly,
but not really noticeable.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/