Name: boT120536 Date: 02/15/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

The use of signed jar files results in about 50% more runtime memory usage
compared with the same jar files unsigned.

You can reproduce this with any signed versus nonsigned jar files.

We want to deploy our application as standalone, as applet and as webstart
application. For the applet and webstart deployment we must sign our jar files.
The big problem now is that the memory encreases from about 30MB to 45MB -->
This is not acceptable for our customers.

What can we do! If this problem cannot be resolved our project may be must stop
using java technology at all!
(Review ID: 117015)
======================================================================