You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Mete Atamel (JIRA)" <ji...@apache.org> on 2012/12/09 15:49:21 UTC
[jira] [Commented] (OAK-461) Commit time is increasing when
performing multiple sequentially commits
[ https://issues.apache.org/jira/browse/OAK-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527486#comment-13527486 ]
Mete Atamel commented on OAK-461:
---------------------------------
I added the test case in rev 1418983. The problem is not commit operation but rather the fact that all the children in the test are being added under the same parent (/). Current MongoMK keeps track of all children of a node in a children array and that slows things down when a single node has a lot of children. The same issue is happening in OAK-440.
> Commit time is increasing when performing multiple sequentially commits
> -----------------------------------------------------------------------
>
> Key: OAK-461
> URL: https://issues.apache.org/jira/browse/OAK-461
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Tudor Rogoz
> Assignee: Mete Atamel
> Attachments: 0001-OAK-461-Commit-time-is-increasing-when-performing-multiple-sequentially-commits.patch
>
>
> See test CommitCommandTest.testCommitTimeRamp
> Bellow are my results:
> 165.0
> 6.0
> 7.0
> 8.0
> 15.0
> 35.0
> 46.0
> 67.0
> 61.0
> 64.0
> 77.0
> 104.0
> 104.0
> 125.0
> 305.0
> 143.0
> 751.0
> 794.0
> 372.0
> 229.0
> 213.0
> 310.0
> 265.0
> 267.0
> 438.0
> 337.0
> 335.0
> 408.0
> 378.0
> 475.0
> 433.0
> 575.0
> 534.0
> 544.0
> 566.0
> 657.0
> 656.0
> 688.0
> 720.0
> 829.0
> Final Results:JAMon Label=commit, Units=ms.: (LastValue=827.0, Hits=1000.0, Avg=317.672, Total=317672.0, Min=4.0, Max=1485.0, Active=0.0, Avg Active=1.0, Max Active=1.0, First Access=Thu Nov 22 10:21:48 EET 2012, Last Access=Thu Nov 22 10:27:05 EET 2012)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira