We seemed to have introduced a significant performance degradation
for the keytool and jarsigner tools on the win32 platform.

To summarize:
**************
Time to completion with JIT
Solaris Win32
------- ------
keytool: 13 seconds 13 minutes (yes, thats minutes)
jarsigner: 14 seconds > 1 hour (killed after 1 hour)

Running without the JIT does *not* make a difference.

Details:
********
Please see the attached out.solaris and out.win32 log files
for detailed time stamps.

keytool and jarsigner commands used:
(these commands are used as part of
the javax (java extensions) test suite
Makefiles, somewhat modified to grab the
time, date stamp info):
****************************************
::::::::::::::
doit
::::::::::::::
make clean
bar
fung
goo
::::::::::::::
bar
::::::::::::::
date
echo "Using keytool..."
keytool -genkey -alias ALA -keystore ./qekeystore -keypass testing123 -dname "cn=QEtest" -storepa
ss testing123
date
::::::::::::::
fung
::::::::::::::
date
echo "Creating the jar..."
jar cvf e8.jar ../pkgs
date
::::::::::::::
goo
::::::::::::::
date
echo "Signing the jar..."
jarsigner -storepass testing123 -keystore qekeystore -keypass testing123 e8.jar ALA
date

echo "Verifying the signed jar..."
jarsigner -verify -verbose -keystore qekeystore e8.jar
date

The hardware:
*************
Solaris:
              MODEL: SUNW,Ultra-1
                CPU: SUNW,UltraSPARC
    FRAME BUFFER(S): cgsix
      SunOS RELEASE: 5.6
             MEMORY: 128MB
               SWAP: 288.8MB total, 113.8MB used, 175.0MB available
       LOAD AVERAGE: 0.03, 0.03, 0.08
 
Win32:
Toshiba Pentium 233
48 MB ram
MS-Win95