[
https://issues.apache.org/jira/browse/SLING-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068167#comment-13068167
]
Carsten Ziegeler commented on SLING-1476:
-----------------------------------------
Interesting! Now, if I increase the iterations, the executor gets slower on my
machine.
For the fun of it, I added another test using AtomicLong and AtomicInt (now, of
course this wouldn't give us the functionality of the statistics object)
and I also changed the tests a little bit by creating the random object just
once (revision 1148627) - things now look completely different.
But at least on my machine, as soon as there is a high iteration and/or a high
number of threads, the diect approach is the fastest
> provide number of processed requests
> ------------------------------------
>
> Key: SLING-1476
> URL: https://issues.apache.org/jira/browse/SLING-1476
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: Engine 2.0.6
> Reporter: Jörg Hoh
> Priority: Minor
> Attachments: org.apache.sling.jmx.zip, result.jpg
>
>
> For status monitoring it would be useful to have the number of total
> processed requests since restart of the JVM. Is it possible to have a
> "statistics" component which could provide such numbers?
> (The "manual" way to do it would be writing a very simple RequestFilter which
> just increments a counter and expose this object as OSGI component.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
