harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgueni Brevnov" <evgueni.brev...@gmail.com>
Subject Re: The way to increase the SPECjAppServer2004 score by 20%
Date Tue, 23 Oct 2007 07:45:29 GMT
Pavel,

I think its not common situation when parent class loader is changed
at runtime. To be honest I don't know how it's possible since parent
class loader is kept in private field. Anyway, can we somehow detect
such situation and switch to normal scheme or discard cached classes
upon switching parent class loader.

Thanks
Evgueni

On 10/22/07, Pavel Pervov <pmcfirst@gmail.com> wrote:
> Looking at the Java Virtual Machine Specification there are two terms:
> initiating loader and defining loader.
>
> Initiating loader is the class loader which was first asked to load class in
> delegation chain (CL2 in your example).
>
> Defining loader is the class loader which has found bytes for class
> definition and called to JNI->DefineClass.
>
> Lets review the following delegation model.
>
> CL1<-CL2<-CL3
>
> CL4<-CL2<-CL5
>
> There is nothing wrong with CL2: its delegation model simply assumes
> switching delegation parent depending on some external property.
>
> Different versions of class Foo are available from CL1 and CL4. Now, we do
> something like CL3.loadClass("Foo") and CL5.loadClass("Foo").
> If CL2 will cache the class Foo, then the call to CL5 will return wrong
> result.
>
> So the caching is possible, but it is only allowed to register class in
> initiating loader and in defining loader. Otherwise, you may have wrong
> classes returned to your application.
>
> Determining defining loader is simple. Can you suggest some working idea on
> how to determine initiating loader for a class?
>
> WBR,
>    Pavel.
>
> On 10/22/07, Sergey Dmitriev <sergey.v.dmitriev@gmail.com> wrote:
> >
> > Hello
> >
> > This letter is actually about HARMONY-4965, I just changed a little
> > bit a subject. :)
> >
> > During my play with SPECjAppServer2004 on OC4J I've found out that we
> > have a way to optimize the class loader. Or in other words currently
> >
> > Lets say we have class loaders CL1 and CL2, and CL2.getParent() ==
> > CL1. And lets say we have a class C which is loaded by the CL1 (the
> > parent one). And then we try to load class via the class loader CL2:
> > of course CL2 first of all tries to load it via its parent CL1 and
> > succeed in it. When we try to load class C via CL2 again we will have
> > the same chain of calls: CL2 -> CL1. But if CL2 have support of
> > caching of classes loaded by not itself - the chain can become much
> > shorter - it could end at CL2.findFinishedClass().
> >
> > For example RI behaves like this. See JIRA's demo.
> >
> > Back to the SPECjAppServer2004 @ OC4J. In this case we have a deeper
> > chain: we have a concrete class which is been searched so deep that we
> > looking for this class in boot strap class path. And this is what we
> > have in steady state of the benchmark. Don't you think it is useless?
> > :)
> >
> > Talking about numbers: my measurements show that we can take up to 20%
> > of burst having this bug fixed. Could some competent guy take a look
> > into this?
> >
> >
> > Thanks
> > Sergey
> >
>
>
>
> --
> Pavel Pervov,
> Intel Enterprise Solutions Software Division
>

Mime
View raw message