Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of gnodet@gmail.com designates
 216.239.58.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=rySss5Kclj0U9iC393LZdE3zhf8My1LRS9FGMUBdkNjsGEIAmP1SdKqAMDavJVsA6DlSwARfS6qHLqVPaBh2p7vYErCJvHzOdYR1XZO3dt2gVsKmrvCHbQlDX+6PE4lp0dYu/AtRErxL+9jXD0AR9NUiLkM2nuYU8ES4sNMFWnI=
Message-ID: <b23ecedc0802250612q5489a27ayce6c4e80648cfb36@mail.gmail.com>
Date: Mon, 25 Feb 2008 15:12:12 +0100
From: "Guillaume Nodet" <gnodet@gmail.com>
To: dev@felix.apache.org, dev@servicemix.apache.org
Subject: Performance problems in classloading
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm currently working on ServiceMix 4 which uses Felix.\

I have some really important performance problems in classloading.
When loading JBI applications (they have some very specific
classloading architecture
that must be implemented to be JBI compliant), 95% of the time  is
spent in the following method:
   R4SearchPolicyCore.diagnoseClassLoadError()
which is not really acceptable.

The problem is that the classloader is built dynamically and does not
completely rely on
OSGi.  For this reason, the classloader of JBI artifacts delegates to
the parent classloader,
then looks inside its own jar.  This means there will be lots of
ClassNotFoundException thrown
by the parents classloader (ultimately by Felix).

Is there any way to maybe speed / disable the diagnoseClassLoadError
method call which
is purely informative ?

I know the design of the JBI classloaders is not really a good fit in
OSGi, so I will investigate
a better solution (leveraging more of OSGi classloaders) anyway, but I
still wanted to report
the problem.

-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/