| performance problems due to numerous ClassLoader calls [message #46243] |
Tue, 18 February 2003 11:04  |
Eclipse User |
|
|
|
Originally posted by: greenyoghurt.sverige.nu
Hi!
We have severe performance problems with our Eclipse IDE, in particular the
performance of our additional components, packed in approx. 160 plugins.
We tried to find out where the problem is with help of JProbe Profiler and
the result, that method
java.lang.ClassLoader.loadClassInternal(String) often claims most of the
time (for numerous calls (300 and more)).
Does anyone know how we could reduce the number of loadClassInternal(String)
calls?
As plugins are depending on each other, we assume that maybe classes in one
plugin A, which is required by plugins B, C, D and E is then loaded 5 times
instead of only one time.
Could this be a possible behaviour or is a class only loaded one single time
and the other plugins depending on plugin A recognize that the class is
already loaded?
What do you think could reduce these numerous classLoader calls?
Would it help to reduce the number of plugins (as each plugin has its own
classloader) ?
Or are there any properties we could set in Eclipse or the VM so that the
performance gets better ?
Is there maybe any possibility to cache the loaded class in order to prevent
other (redundant) loads of the same class ??
Thanks a lot in advance if someone could help us.
Best regards,
Marion
|
|
|
| Re: performance problems due to numerous ClassLoader calls [message #46274 is a reply to message #46243] |
Tue, 18 February 2003 11:40  |
| Eclipse User |
|
|
|
Originally posted by: dwhitema.us.ibm.com
you should ask this on eclipse.tools for a wider audience and a more
appropriate forum
"marion schmid" <greenyoghurt@sverige.nu> wrote in message
news:b2tjuh$uki$1@rogue.oti.com...
> Hi!
> We have severe performance problems with our Eclipse IDE, in particular
the
> performance of our additional components, packed in approx. 160 plugins.
> We tried to find out where the problem is with help of JProbe Profiler and
> the result, that method
> java.lang.ClassLoader.loadClassInternal(String) often claims most of the
> time (for numerous calls (300 and more)).
>
> Does anyone know how we could reduce the number of
loadClassInternal(String)
> calls?
> As plugins are depending on each other, we assume that maybe classes in
one
> plugin A, which is required by plugins B, C, D and E is then loaded 5
times
> instead of only one time.
> Could this be a possible behaviour or is a class only loaded one single
time
> and the other plugins depending on plugin A recognize that the class is
> already loaded?
>
> What do you think could reduce these numerous classLoader calls?
> Would it help to reduce the number of plugins (as each plugin has its own
> classloader) ?
> Or are there any properties we could set in Eclipse or the VM so that the
> performance gets better ?
> Is there maybe any possibility to cache the loaded class in order to
prevent
> other (redundant) loads of the same class ??
> Thanks a lot in advance if someone could help us.
>
> Best regards,
>
> Marion
>
>
|
|
|
| Re: performance problems due to numerous ClassLoader calls [message #590386 is a reply to message #46243] |
Tue, 18 February 2003 11:40 |
| Eclipse User |
|
|
|
you should ask this on eclipse.tools for a wider audience and a more
appropriate forum
"marion schmid" <greenyoghurt@sverige.nu> wrote in message
news:b2tjuh$uki$1@rogue.oti.com...
> Hi!
> We have severe performance problems with our Eclipse IDE, in particular
the
> performance of our additional components, packed in approx. 160 plugins.
> We tried to find out where the problem is with help of JProbe Profiler and
> the result, that method
> java.lang.ClassLoader.loadClassInternal(String) often claims most of the
> time (for numerous calls (300 and more)).
>
> Does anyone know how we could reduce the number of
loadClassInternal(String)
> calls?
> As plugins are depending on each other, we assume that maybe classes in
one
> plugin A, which is required by plugins B, C, D and E is then loaded 5
times
> instead of only one time.
> Could this be a possible behaviour or is a class only loaded one single
time
> and the other plugins depending on plugin A recognize that the class is
> already loaded?
>
> What do you think could reduce these numerous classLoader calls?
> Would it help to reduce the number of plugins (as each plugin has its own
> classloader) ?
> Or are there any properties we could set in Eclipse or the VM so that the
> performance gets better ?
> Is there maybe any possibility to cache the loaded class in order to
prevent
> other (redundant) loads of the same class ??
> Thanks a lot in advance if someone could help us.
>
> Best regards,
>
> Marion
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03856 seconds
Home