[
https://issues.apache.org/jira/browse/JCR-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3040:
---------------------------------
Attachment: jr-test.log
JCR-3040.patch
point taken on the patch.
I've rolled-back everything, and I'm not re-submitting the JMX Session stats as
a patch.
I've also ran the performance tests (ConcurrentReadTest and
ConcurrentReadWriteTest) and attached the results, to analyze the performance
impact.
The problem with these tests is that I ran them on my machine, which I think is
error-prone as it is also dependent on the background noise. I've tried to not
stress it much (no eclipse running, etc), but I guess it is not 100% bullet
proof.
It would be interesting to run the tests on a continuous integration machine,
if there is any available.
In jr-test.log, you'll find the test results. I ran them 5 times, each time
running the 2 versions of the code (with and without my changes to the session
state object).
I'm really interested in your opinion about the test results.
> JMX Stats for the Session
> -------------------------
>
> Key: JCR-3040
> URL: https://issues.apache.org/jira/browse/JCR-3040
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Attachments: JCR-3040.patch, jr-test.log
>
>
> I've named them Core stats. This will include:
> - number of sessions currently opened
> - session read / write operations per second
> The stats refresh once a minute.
> This is disabled by default, so it will not affect performance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
