JDK-4466510 : Memory Use Problem
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0,1.3.1,1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic,windows_2000
  • CPU: generic,x86
  • Submitted: 2001-06-05
  • Updated: 2004-05-21
  • Resolved: 2004-05-04
Related Reports
Duplicate :  
JDK-4607284 - improve memory footprint of the JVM
Description

Name: bsC130419			Date: 06/05/2001


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


God Help us!  You guys have done an awesome job on Performance, but Memory
usage is pitiful.

Here is the scoop - I am writing the GUI for the new iPlanet Instant Messaging
app and memory use is unreal.  The reason i am submitting this as a bug is
because if my client application is run under Microsoft's Evil JVIEW (swing is
being used), it uses FAR less memory!!

My client running with Jview uses around 10MB of Memory and will grow to 16MB
after a lot of use.  I thought that was pretty bad.

Java 1.3.1 Starts up at 15MB - 5MB more than JVIEW and grows to somewhere
around 25MB running similar tests.

Java 1.4.beta now starts up at almost 20MB - but i will admit that the memory
management seems to be a little better because it still only grows to 25MB.

For a server app, this is fine - The real problem is that this is a simple
client.

Other test run by loading a simple JFrame with a few components added show
JVIEW at 6MB and Suns Java still at 10MB or more!

** When you try to sell something like this to a customer and a simple
application uses more memory than any other app on their system - you have a
real problem!
(Review ID: 125887) 
======================================================================
Comments
EVALUATION This feature is being tracked as 4607284 (improve jvm footprint) and 4665470 (improve rest of j2se footprint) for the 1.5 release ###@###.### 2002-08-05 ###@###.### 2004-05-04 The Java platform does use a lot amount of memory to execute simple Java applets and applications. Reducing the amount of memory used (footprint) is one of a number of priorities for the J2SE team. Some improvements in memory usage have been made in the 1.5 release. While reducing footprint will remain one of the J2SE team's priorities, this particular bug report is not helpful in driving the issue. Since this bug report does not descibe any specific action or any specific goal, there is no clear definition of "fixed". As there have been some improvements in the 1.5 release, I am closing this bug as a duplicate of 4607284. Setting goals for footprint reduction will be an important part of project planning for future releases. ###@###.### 2004-05-11 In recent releases, memory mapped files and devices are used for more purposes. This increases the footprint, as measured by some tools, without actually increasing the amount of physical memory consumed. As an example, in 1.3.1 and 1.4.0, on Solaris, the framebuffer (some types) is mapped into the address space and manipulated directly by the X client library (DGA). Also, in 1.5.0 the class data sharing mechanism maps a file into the address space, which increases the amount of the virtual address space used. This decreases the overall amount of physical memory used because fewer pages from boot jar files and fewer pages from the java heap are required. These benefits do not show up in some measurements, especially on Windows, where the boot jar files are not mapped.
11-06-2004
WORK AROUND Name: bsC130419 Date: 06/05/2001 pray ======================================================================
11-06-2004
PUBLIC COMMENTS The Java platform does use a lot amount of memory to execute simple Java applets and applications. Reducing the amount of memory used (footprint) is one of a number of priorities for the J2SE team. Some improvements in memory usage have been made in the 1.5 release. While reducing footprint will remain one of the J2SE team's priorities, this particular bug report is not helpful in driving the issue. Since this bug report does not descibe any specific action or any specific goal, there is no clear definition of "fixed". As there have been some improvements in the 1.5 release, I am closing this bug as a duplicate of 4607284. Setting goals for footprint reduction will be an important part of project planning for future releases.
10-06-2004