Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <449318016.398811264095594478.JavaMail.jira@brutus.apache.org>
Date: Thu, 21 Jan 2010 17:39:54 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-1459) Adding members to a groupOfNames
 results in polynomial increase in JDBM partition size
In-Reply-To: <1101337719.352021263941154510.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSERVER-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803384#action_12803384 ] 

Emmanuel Lecharny commented on DIRSERVER-1459:
----------------------------------------------

This is not a problem with the Add operation. If I add 10 000 values to the attribute, the MasterDB size grows up to 1 Mb, no more. 

It's a problem with the Modify operation : adding 500 times a value make the Master.db growing up to 17 Mb. 

PS: I have created a new tests, no need to send me the SimpleRegression class.

> Adding members to a groupOfNames results in polynomial increase in JDBM partition size
> --------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1459
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1459
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.5
>         Environment: Any (tested on Linux and Mac OS X)
>            Reporter: Ben Hoyt
>            Priority: Blocker
>             Fix For: 2.0.0-RC1
>
>         Attachments: DIRSERVER-1459.tar.gz, screenshot-1.jpg
>
>
> I noticed a polynomial increase JDBM partition size and therefore disk usage when adding users to groups in my ApacheDS instance.  The vast majority of the usage (95+% once you hit a couple thousand users) is in workingDirectory/partitionId/master.db  
> Further testing showed that simply adding a user is linear, as one would expect, and as 'apacheds-tools capacity' confirms.  It is only when a user is made a member of a group that the JDBM partition size shoots up.
> Example statistics:
> Add 16,000 users - JDBM partition size = ~70 megabytes
> Now add those same 16,000 users to a single group (all in the same group) - JDBM partition size = ~19 GIGABYTES
> I'll work to attach a test case and some more numbers from my tests

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.