Details

    • Type: Epic
    • Status: Defining
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: SERVER 6.y
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Threadsafe Puppet
    • Template:
    • Team/s:
      Server
    • Epic Status:
      To Do
    • QA Risk Assessment:
      Needs Assessment

      Description

      With the introduction of CD4PE's Impact Analysis, agentless device nodes, and compiling code snippets for Bolt, Puppet Server's ability to scale is more important than ever. Much of our current bottleneck comes from the need to only process one request per JRuby instance at a time, leading to the need to maintain a resource-heavy pool of JRuby instances. The JRuby pool also appears to be the largest generator of support escalations for Puppet Server. One of the main benefits of JRuby over MRI Ruby is its ability to use real multi-threading, but the Puppet codebase itself is not threadsafe, so we are completely missing out on this advantage. If we can make the Puppet codebase threadsafe, we unlock a large amount of scalability within our current architecture, while also having an opportunity to clean up some of the largest sources of technical debt.

      This would be a win both for customer and developer efficiency and scalability.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                lizzi Lizzi Lindboe
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support