Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4510002

Hotspot verbosegc logs not just as adequate as EVM verbosegc logs.

XMLWordPrintable

    • gc
    • mantis
    • generic, x86, sparc
    • generic, solaris_8, windows_2000

      The hotspot VM's -verbosegc -verbosegc (twice) output is not as adequate as from jdk1.2.2_0x production releases.

      Would be nice to have the following in hotspot VM's:

      1. Time stamp of the GC activity
      2. Size and no. of objects allocated per GC interval
      3. Size and no. of objects promoted per GC
      4. Application time every Gc interval
      5. % of free memory at every GC
      6. memory allocated/free at the semispace/Eden level for every young GC
      7. Semispace sizes

       
      And any additional information given by the second -verbosegc option on EVM.
      Also, if the format of output be kept the same in hotspot as EVM, it would be a bonus and would make life simpler.

      This information can be extremely useful for analysing application behaviour wrt to GC, hence tuning the application as well as the JVM environment wrt to JVM memory options and switches.

            rverabel Raghu Verabelli (Inactive)
            duke J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: