[
https://issues.apache.org/jira/browse/FELIX-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086323#comment-16086323
]
Karl Pauls commented on FELIX-5665:
-----------------------------------
Well, the URLHandlers might be a red herring but from your description, there
are two places I can think of that do different things inside OSGi/Felix and
outside namely, class/resource look-up and URL handling. Granted, I don't think
URL handling should cause extra calls to findClassOrResourceByDelegation but it
might be possible it somehow does.
Anyways, yes, please try to see if there is a lot of resource look-up going on
first. Otherwise, it might be worthwhile to look at the callstack for
findClassOrResourceByDelegation in your profiler and see what the place is that
triggers all the calls (and in that, it might be interesting to lookout for URL
related places).
> High CPU usage on
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation
> ---------------------------------------------------------------------------------------------
>
> Key: FELIX-5665
> URL: https://issues.apache.org/jira/browse/FELIX-5665
> Project: Felix
> Issue Type: Bug
> Affects Versions: framework-5.6.4
> Reporter: AnilKumar Attuluri
> Attachments: IMG_1.jpg, IMG_2.jpg
>
>
> We have been running some performance tests to prepare our OSGi bundle
> (*running in Apache Karaf*) for production.
> Just to give some background about our OSGi bundle, we converted an existing
> Spring application into an OSGi bundle with all the current dependencies
> packaged into the bundle as an uber artifact.
> When we run >= 500 TPS (each of these calls results in a http call made via a
> library) we run into this high CPU usage spikes reaching up to 100% CPU.
> Please see the image attached, the spikes in the image are 100% CPU usage
> while the average is about 40%. Also see the CPU sampler image which points
> to
> *org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation*
> Is there an existing bug/documentation that already captures this?
> We don't see this behavior when we run the same app in standalone JVM.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
