Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-12059

Enhance Memory information on System Information Page

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      The current Memory information for the system information page can be confusing to users. As it basically reports to you the current memory usage levels, this can be misleading and result in users to believing the JVM parameters parsed to the JVM do not take effect or have not been configured correctly when in fact they have.

      For example, when setting the boundaries for the memory with varying -Xms and -Xmx settings, Confluence initially shows memory usage up to the minimum memory setting. As the usage increases, it will eventually be updated in the system info page to reflect the current usage levels.

      Example, this is the current Heap size settings for my 2.8.0 instance:

      # Initial Java Heap Size (in MB) 
      wrapper.java.initmemory=512m 
       
      # Maximum Java Heap Size (in MB) 
      wrapper.java.maxmemory=756m 
      

      The screenshot shows the current total at 508 MB. Some users with this configuration would expect to see total memory as 756 MB instead. Perhaps we can include a script that can be run to retrieve memory information on demand? I've attached an example jsp i wrote which grabs information on the current JVM properties:

      # Java version:  1.5.0_13
      # Java Home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
      # Java classpath: ../wrapper/lib/wrapper.jar:/Library/Java/Home/lib/tools.jar:../bin/bootstrap.jar
      # Total Memory: 532873216
      # Max Memory: 786628608
      # Free Memory: 386200112
      

      Something like this could be useful for checking and validating actual memory settings rather than the current usage.

        Attachments

        1. jvm-properties.jsp
          0.7 kB
        2. memory.png
          memory.png
          14 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ktran Kevin Tran [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: