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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/10/09 16:26:46 UTC

[jira] [Resolved] (OAK-462) Performance spikes when multiple mks are writing to the same database

     [ https://issues.apache.org/jira/browse/OAK-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-462.
----------------------------------

    Resolution: Won't Fix

Won't fix. This issue was created for the first version of the MongoMK.

> Performance spikes when multiple mks are writing to the same database
> ---------------------------------------------------------------------
>
>                 Key: OAK-462
>                 URL: https://issues.apache.org/jira/browse/OAK-462
>             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 ConcurrentWriteMultipleMkMongoTest.testThousandNodes.
> When multiple mks are writing in parallel into the same database, at some point, the time needed for performing a specific commit is too big.
> I get for example 22 seconds spikes for one commit, where the average is 0.3 seconds.



--
This message was sent by Atlassian JIRA
(v6.1#6144)