Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2396

Revise computation of default-max-command size

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2

      Description

      Notes:

      • config.clj currently sets the JMS max-frame-size to 200MB by default
      • the JMS frame size sets an upper bound on the command size
      • a 164MB JSON catalog string produces a ~200MB JMS message
      • at rest, after startup PDB currently consumes about 60MB RAM
      • the forthcoming dump-heap command can help recompute that value (i.e. override process-command as per the also forthcoming acceptance.max-command-size, and add a call, then open the HPROF file in mat, visualvm, etc.).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              rob.browning Rob Browning
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support