Feedback from tester:
---------------------

I have noticed an increase in performance with Hotspot! However, the
garbage collector seems to be a little to aggressive at cleaning up
SoftReferences. I have not experimented with the other Reference types,
but a Soft Reference is the strongest anyway.


I am implementing a cache and there is a huge difference when running with
HotSpot. Without it, I get very efficient caching. With HotSpot I loose my
reference almost right away there by slowing this section of my app
significantly, far below what it was without HotSpot. (It has to make a
call to a server to get the data that is not cached.)


---
I am using jdk 1.2.1 (with the huge memory leak causing my app to take
anywhere between 20-40MB of memory. I am running NT4 SP4 on a PII-333 with
128MB of RAM. I as using the fcs release of HotSpot.


Mark Claassen
Donnell Systems, Inc.
300 S. St Louis Blvd.
South Bend, IN 46617
(219)232-3784
(219)232-4014 (fax)
###@###.###


Name: krT82822 Date: 12/17/99


java version "1.2.2"
Java HotSpot(TM) Server VM (2.0rc1, mixed mode, build I)

See Bug #4239645.

Essentially the HotSpotVM is treating a SoftReference just like a
WeakReference, so that any implementation of a cache is rendered useless.
(Review ID: 99113)
======================================================================