[
https://issues.apache.org/jira/browse/POOL-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145654#comment-14145654
]
Bernd Eckenfels commented on POOL-277:
--------------------------------------
[~lpouzac] we are still discussing (on the commons-dev mailing list) why we do
not see very clear speed advantages when running some benchmarking. We do
wonder if the profiler does lie here (as this is a very speedy operation). Do
your tests also have some form of overall score or measurement, where you see
clearly better performance and can you tell us what kind of operations
(especially how often objects are created and how slow the creation and
verification is) you actually tested. With less frequent borrows I would expect
the code to be less contended but also less relevant to the overall performance.
> Monitor contention at BaseGenericObjectPool
> -------------------------------------------
>
> Key: POOL-277
> URL: https://issues.apache.org/jira/browse/POOL-277
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Lucas Pouzac
> Labels: concurrency, performance
> Fix For: 2.3
>
> Attachments: monitor_contention_basegenericobjectpool.png,
> monitor_contention_basegenericobjectpool_after_pull_request.png,
> nolockstats2.patch
>
>
> Updating JMX causes synchronization while the service is secondary. See
> screenshot.
> I create a Pull Request [#1|https://github.com/apache/commons-pool/pull/1].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
