You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org> on 2011/11/09 12:38:51 UTC
[jira] [Updated] (JCR-3064) Concurrent access performance drop
[ https://issues.apache.org/jira/browse/JCR-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3064:
-------------------------------
Attachment: ConcurrentReadWriteTest-2.3.png
ConcurrentReadTest-2.3.png
I ran the performance tests over all Jackrabbit trunk commits since 2.2 was branched. The attached -2.3.png graphs show a pretty clear increase around revisions 1043xxx.
The table below shows the median timings for each Jackrabbit revision in this period after which the performance again settles to a stable though slower state.
revision read r/w
=====================
1043084 111 127
1043085 136 132
1043086 124 128
1043088 119 150
1043343 129 136
1043357 128 138
1043358 124 140
1043430 477 1899
1043541 112 122
1043545 106 115
1043546 109 119
1043554 496 1947
1043555 110 128
1043598 112 120
1043616 579 2127
1043618 499 1722
1043623 114 124
1043637 504 1997
1043642 106 137
1043656 536 2040
1043657 108 123
1043663 105 135
1043893 506 2058
1043897 479 1885
> Concurrent access performance drop
> ----------------------------------
>
> Key: JCR-3064
> URL: https://issues.apache.org/jira/browse/JCR-3064
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Jukka Zitting
> Priority: Blocker
> Fix For: 2.4
>
> Attachments: ConcurrentReadTest-2.3.png, ConcurrentReadTest-2011.png, ConcurrentReadTest.png, ConcurrentReadWriteTest-2.3.png, ConcurrentReadWriteTest-2011.png, ConcurrentReadWriteTest.png, JCR-3064-EntryCollector.patch, visualvm-ConcurrentReadTest-2.2.png, visualvm-ConcurrentReadTest-2.3.png
>
>
> Our performance tests show a pretty bad drop in concurrent access performance (both read and write) in the latest trunk when compared to Jackrabbit 2.2. We need to track down the cause and fix it before the 2.3 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira