| What about the performance of OSGI based runtime? [message #219000] |
Wed, 31 March 2004 03:59  |
Eclipse User |
|
|
|
This is a multipart message in MIME format.
--=_alternative 0031E897C1256E68_=
Content-Type: text/plain; charset="US-ASCII"
Compared to the runtime of Eclipse 2.x, is the performance of the OSGI
based Runtime better than before? Are there any options to "tune" the
performance of the 3.0 Runtime?
--=_alternative 0031E897C1256E68_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=1 face="sans-serif">Compared to the runtime of Eclipse 2.x,
is the performance of the OSGI based Runtime better than before? Are there
any options to "tune" the performance of the 3.0 Runtime?</font>
--=_alternative 0031E897C1256E68_=--
|
|
|
|
| Re: What about the performance of OSGI based runtime? [message #224436 is a reply to message #220400] |
Thu, 08 April 2004 07:05  |
| Eclipse User |
|
|
|
This is a multipart message in MIME format.
--=_alternative 003D749EC1256E70_=
Content-Type: text/plain; charset="US-ASCII"
Maybe "tuning" is not the correct expression. I thought that there are
some hints to improve the startup performance ...
Anyway, I've another question concerning the OSGI "kernel": I've read that
there is a new classloading mechanism. In Eclipse 2.x, the classloader
mechanism was PSP (I understand this mechanism). Now it is PP|S, i.e. the
classloader asks first the parent classloader,
then either a single prerequisite known to contribute classes in the
package being queried and then the own classpath entry.
But how does the classloader know what single prerequisite it has to ask?
Is this new classloading mechanism one of the reasons that the OSGI
runtime performs better than before? As far as I understand it will
not "go through" all the dependencies if a class is not in the
corresponding plug-in itself, to find the class, but to the appropriate
prerequisite directly, right?
--=_alternative 003D749EC1256E70_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=1 face="sans-serif">Maybe "tuning" is not the
correct expression. I thought that there are some hints to improve the
startup performance ...</font>
<br><font size=1 face="sans-serif">Anyway, I've another question concerning
the OSGI "kernel": I've read that there is a new classloading
mechanism. In Eclipse 2.x, the classloader</font>
<br><font size=1 face="sans-serif">mechanism was PSP (I understand this
mechanism). Now it is PP|S, i.e. the classloader asks first the parent
classloader,</font>
<br><font size=1 face="sans-serif">then either a single prerequisite known
to contribute classes in the package being queried and then the own classpath
entry.</font>
<br><font size=1 face="sans-serif">But how does the classloader know what
single prerequisite it has to ask?</font>
<br><font size=1 face="sans-serif">Is this new classloading mechanism one
of the reasons that the OSGI runtime performs better than before? As far
as I understand it will</font>
<br><font size=1 face="sans-serif">not "go through" all the dependencies
if a class is not in the corresponding plug-in itself, to find the class,
but to the appropriate prerequisite directly, right?</font>
--=_alternative 003D749EC1256E70_=--
|
|
|
Powered by
FUDForum. Page generated in 0.38720 seconds
Home