Observe user'ss ulimit's in setting default heap size.

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Duplicate
    • Priority: P3
    • None
    • Affects Version/s: 7
    • Component/s: hotspot
    • None
    • gc
    • generic
    • generic

      When the default heap size is chosen ergonomically, observe the
      user's memory size limits (ulimits).
      Customer scenario:
      A container with capped-memory=16GBis created in a E25k domain that has 64GB of physical memory. The "capped-memory" in a zone is a soft memory limit not a hard partitioning memory limit like in LDoms. There is 'rcapd' daemon running in the background to check if a zone's processes are hitting the "capped-memory" limit. Sun's JVM by default uses 1/64th of physical memory as its initial heap size, therefore in a 64GB domain, a container will use 1GB as its default heap size. Customer desires to have other method to define a default Java heap size.

      Kimberly Chang
      Systems Engineer

            Assignee:
            Unassigned
            Reporter:
            Jon Masamitsu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: