Name: ca25432 Date: 12/13/2001



Provide more performance and logging characteristics for a JRE "out of the box"
The information should be simple enough for a non-VM engineer to be able to
understand, in particular for gc/JVM performance tuning. And for logging, simple
levels of logging that a end user could turn on

======================================================================

I'm going to add clarification to this bug. It will act as a central placeholder for a number of subtasks which are too small to put into the Tiger feature database. There will be work in the GC, C2 and probably the runtime as well.

This should remove the need for explicit GC tuning on 90% or more of typical server Java applications. When explicit tuning is required it should be done using flags that describe the requirements of the application, not the requirements of the garbage collector.

There choice between HotSpot compilers should be made automatically and optimally for 90% or more of typical server Java applications. The runtime should use information about the machine configuration and other information to make this choice.

The runtime should select the best OS libraries (ie threading, malloc, etc) without requiring user intervention. The runtime should also automatically select an appropriate page-size and other system variables.