felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5363) new URL(string) suffers under concurrency
Date Fri, 23 Sep 2016 19:07:20 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517287#comment-15517287

Karl Pauls commented on FELIX-5363:

Yeah, thats why I was asking if you had more than one framework. As you don't, it pretty much
must be just the double lock that needs to be acquired. This code was written before we had
java.util.concurrent (or at least while we where still targeting < 1.5) but as we are past
that it should be easy to make this bottleneck go away. 

Will you be able to run your set-up in question with a patched version of felix (if so, I'll
try to get you a patch that hopefully performs better)? 

> new URL(string) suffers under concurrency
> -----------------------------------------
>                 Key: FELIX-5363
>                 URL: https://issues.apache.org/jira/browse/FELIX-5363
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-5.4.0
>            Reporter: Rob Ryan
>            Assignee: Karl Pauls
>         Attachments: Merged-callees.csv
> Under moderate concurrency (25threads) and frequent use of new java.net.URL(string) a
bottleneck was seen with yourkit.  In one test involving HTML page generation new URL(url)
was seen to take 20% of time (via yourkit).
> This was tracked to org.apache.felix.framework.URLHandlers.getFrameworkFromContext()
URLHandlers.java which accounted for 99% of the time used by new URL(url).

This message was sent by Atlassian JIRA

View raw message