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 18:38:21 GMT

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

Karl Pauls commented on FELIX-5363:

Hm, maybe I'm reading this wrong but it looks to me like it isn't actually URLHandlersStreamHandlerProxy.getStreamHandlerService()
 but rather URLHandlers.getFrameworkFromContext() which is the culprit (time v.s. own time).
That would make sense to me as it is potentially a expensive call (depending on what you are
doing, you might be able to disable the url handlers with felix.service.urlhandlers=false
but that likely has to many sideeffects). 

However, you shouldn't necessarily run into the expensive part of it - are you running more
than one framework at the same time? 


> 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
>         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.URLHandlersStreamHandlerProxy.getStreamHandlerService()
URLHandlersStreamHandlerProxy.java which accounted for 99% of the time used by new URL(url).

This message was sent by Atlassian JIRA

View raw message