Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64861

Java applications have degraded performance on Windows Server 2008+ agents when started via Task Scheduler

XMLWordPrintable

      Technically this is not a Jenkins problem.

      But I think, this problem can potentially affect many users, so it would be nice to have it in documentation or at least as known issue here.

      So we have windows agents connected to server via JNLP. To make agents connect to server after each restart / revert, I created a task in Windows scheduler to kick a bat, which starts agent.jar
      The problem is, that Windows scheduler in Windows 2016 starts all the tasks in "below normal" priority.
      So java process, executing agent.jar is run in "below normal" priority too.
      And when we run our Java application on agent via Jenkins job or script, the application's process starts in "below normal" priority as well. Which increase execution time roughly twice, comparing to manual start on the same agent. Even when I go to agent and change Java application priority manually to "high" right after it is started, that does not help.

      There is no "priority" option when windows scheduler creates tasks, but you can fix it by exporting task to XML, editing its "Priority" tag and importing it back (after deleting original task of course).
      After setting priority to "normal" this way execution time returns to normal.

        1. JenkinsAgent.xml
          3 kB

          [JENKINS-64861] Java applications have degraded performance on Windows Server 2008+ agents when started via Task Scheduler

          Helder Magalhães added a comment -

          Just stumbled on this "issue" (unexpected behavior).

           

          Technically this is not a Jenkins problem.

          Agreed, I'm proposing a reshape of the issue into a documentation task in the hope that it is featured in a KB article or a FAQ entry.

           Although the description is sufficient, I'm leaving a couple tightly related references:

          1. Windows Task Scheduler: changing task-priority
          2. Windows system performance is slow because _mprosrv processes are paging

          Helder Magalhães added a comment - Just stumbled on this "issue" (unexpected behavior).   Technically this is not a Jenkins problem. Agreed, I'm proposing a reshape of the issue into a documentation task in the hope that it is featured in a KB article or a FAQ entry.  Although the description is sufficient, I'm leaving a couple tightly related references: Windows Task Scheduler: changing task-priority Windows system performance is slow because _mprosrv processes are paging

          Helder Magalhães added a comment -

          A bit of additional research seems to confirm that the issue seems to start in Windows Server 2008 (R2?):
          Windows 2008 Task Scheduler Automatically Downgrades Thread Priority

          Linked articles and my own experience (Windows Server 2019) show that this behavior is Server 2008+ (subject updated accordingly).

          Helder Magalhães added a comment - A bit of additional research seems to confirm that the issue seems to start in Windows Server 2008 (R2?): Windows 2008 Task Scheduler Automatically Downgrades Thread Priority Linked articles and my own experience (Windows Server 2019) show that this behavior is Server 2008+ (subject updated accordingly).

            Unassigned Unassigned
            alpanshin Alexandr Panshin
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: