Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1740

Suggest guidance around ReservedCodeCacheSize

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: DOCS
    • Labels:
      None
    • Environment:

      Oracle JDK 1.8.0-112
      Puppet Server 2.7.2

    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      Can anyone provide some guidance around the settings for Code cache size? We run into this issue every few days or so on a moderately busy puppet master:

      Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled.
      Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=
      CodeCache: size=2097152Kb used=2088471Kb max_used=2089485Kb free=8680Kb
       bounds [0x00007f0a9c000000, 0x00007f0b1c000000, 0x00007f0b1c000000]
       total_blobs=146735 nmethods=146066 adapters=570
       compilation: enabled
      

      We've already increased to the max amount of 2g.

      Here's our JVM args;

      JAVA_ARGS="-Xms32g -Xmx32g -XX:+UseCodeCacheFlushing -XX:ReservedCodeCacheSize=2g
      

      And we still get this error and there's nothing to do besides restart the entire puppetserver process.

          max-active-instances: 15
          max-requests-per-instance: 500
          compile-mode: jit
      

      When the compiler is disabled, we get compilation times like this:

      2017-03-03 17:59:55,793 severity=INFO thread=qtp1270041535-5373 class=puppetserver message="Puppet Compiled catalog for blahblahblah in environment develop in 6272.99 seconds"
      

      Anyone run into this?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ajf Andrew Forgue
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support