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

Consider allowing JRuby compile.mode setting to be end-user configurable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.3.0
    • Component/s: DOCS
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      Server Emerald 2016-01-13, Server Emerald 2016-01-27

      Description

      Through some work done for SERVER-993, we discovered that there could be a considerable performance benefit in at least some scenarios to having Puppet Server use the "compile.mode" setting of JIT instead of the Puppet Server default of OFF when initializing JRuby ScriptingContainers.

      To allow for others to experiment with this for performance, it might be good to expose this as a configurable setting, e.g., via the jruby-puppet section in Trapperkeeper configuration, rather than having it just be hard-coded / unchangeable in Puppet Server code - see https://github.com/puppetlabs/puppet-server/blob/puppet-server-2.2.0/src/clj/puppetlabs/services/jruby/jruby_puppet_internal.clj#L35.

      Probably best to stick with OFF as the default value for now until such time as we might have done sufficient characterization to recommend the use of JIT. Note that JIT is the default value used when running JRuby from the command line.

      For more about the compile.mode setting, see https://github.com/jruby/jruby/wiki/JRubyCompiler#tweaking-and-troubleshooting.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  erik Erik Dasher
                  Reporter:
                  jeremy.barlow Jeremy Barlow
                  QA Contact:
                  Erik Dasher
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: