JDK-6233917 : Change default heap sizes based on performance data
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 6
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: linux_redhat_9.0
- CPU: x86
- Submitted: 2005-02-28
- Updated: 2010-04-02
- Resolved: 2005-11-22
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b59aFixed  |
Related Reports
|
Relates :
|
Description
As part of the mustang performance work we ran a bunch of apps with varying heap numbers to gauge the impact on startup. After much analysis and debate we arrived at a size of 1mb for the young generation and 4mb for the tenure generation.
For reference here's the heap size (on linux) of the set of apps we used after startup:
abeille 576 2520
columba 960 11948
jdiskreport 576 6152
jedit 576 2268
limewire 576 4144
notepad 576 1408
photomesa 576 3372
reportmill 576 6248
----- ------
Average 624 4757
This resulted in an average startup gain of 5%.
###@###.### 2005-2-28 19:37:32 GMT
Comments
|