Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Which Jar Files To Transform?

0 views
Skip to first unread message

Brian McCullars

unread,
Jul 18, 2002, 10:17:39 AM7/18/02
to
Does anyone know which jar files to transform to get the biggest bang for
you buck?


Lisa Wellman

unread,
Jul 19, 2002, 12:39:36 PM7/19/02
to
A couple of other points:
1. The WAS runtime is shipped with JVAPGM objects on most parts. JARs that are used less are shipped with a
lower optimization.
2. For the majority of applications, the amount of application code is very small compared to the WAS
runtime. In these cases JVAPGMs for application code will have little if any effect.
3. Very large applications or large utility libraries (such as the Toolbox) can benefit from JVAPGMs. See
the documentation, including the link Jim provided, for more information on using JVAPGMs in such cases.

Jim Beck wrote:

> If you're using WAS 3.5, you'd have to try some different combinations to
> decide what the right tradeoffs are between performance and space for your
> application. Might want to look at
> http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/as400v35/docs/admopt.html
> first - it doesn't help to transform things loaded through the WebSphere
> class loaders.
>
> If you're on WAS 4.0, there very little that can take advantage of CRTJVAPGM
> as most everything in the application is loaded through WebSphere class
> loaders.

Jim Beck

unread,
Jul 19, 2002, 12:23:08 PM7/19/02
to
If you're using WAS 3.5, you'd have to try some different combinations to
decide what the right tradeoffs are between performance and space for your
application. Might want to look at
http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/as400v35/docs/admopt.html
first - it doesn't help to transform things loaded through the WebSphere
class loaders.

If you're on WAS 4.0, there very little that can take advantage of CRTJVAPGM
as most everything in the application is loaded through WebSphere class
loaders.

0 new messages