[
https://issues.apache.org/jira/browse/JCR-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3064:
-------------------------------
Attachment: ConcurrentReadWriteTest-2011.png
ConcurrentReadTest-2011.png
To help narrow down the cause of the problem I ran the concurrent performance
tests over Jackrabbit trunk from each week of this year. See the attached -2011
graphs for the results.
Based on these measurements it looks like the problem was introduced already
late last year after we branched 2.2. I'll run another series of tests to
better isolate the troublesome change.
> 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-2011.png, ConcurrentReadTest.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
