Two executors on an agent

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Answered
    • None
    • Component/s: None
    • None

      In Jenkins, I can name a "node" (aka agent) to have a "# of executors." I have not found that setting in Bamboo. We are underutilizing the CPU on our agents without that setting.

      This attached screenshot of CPU usage was taken for my agent during a single build. As you can see, we are underutilizing the machine. I'd like to run another job from another build.
      My goal, by the way, is not 100% CPU usage. I know it's not practical. But my goal is > 50%, anyway, and I'd rather not define another agent on the same machine which is exactly the same capabilities.

      As hardware continues to scale with numbers-of-cores on the same machine and IO bandwidth continues to speed, it doesn't make sense to confine an agent to run only one thing at a time.

      This was originally reported with BSP-17485.

        1. cpu-underutilized.png
          80 kB
          Tyler Mace

            Assignee:
            Unassigned
            Reporter:
            Tyler Mace
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: