Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 18 Sep 2014 18:22:35 +0000 (UTC)
From: "Bernd Eckenfels (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12742396.1411030793000.68151.1411064555554@Atlassian.JIRA>
In-Reply-To: <JIRA.12742396.1411030793000@Atlassian.JIRA>
References: <JIRA.12742396.1411030793000@Atlassian.JIRA>
 <JIRA.12742396.1411030793592@arcas>
Subject: [jira] [Commented] (POOL-277) Monitor contention at
 BaseGenericObjectPool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/POOL-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139287#comment-14139287 ] 

Bernd Eckenfels commented on POOL-277:
--------------------------------------

I could work on a change based on the Atomic approach. I am waiting currently on feedback on dev@commons. Maybe you could followup there with details in your test (I wonder why it shows so much concurrency for a simple arithmetic critical section). I assume your pooled objects are actually mocks or very leightweight?

> 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
>
>
> 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)