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

Performance problems on scan on huge Jenkins instances

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • token-macro-plugin
    • None
    • Jenkins 1.584
      Build Failure Analyser 1.12.1

      Hi,

      On a Jenkins 1.584, using Build Failure Analyser 1.12.1, we host more than 2600 jobs, and we have 123 different BFA rules.

      Our log files can be fairly big (ranging from 5Mb to 100 Mb in some exceptional cases) and we have started to have serious performance issues, where the BFA scan on a failing build can take up to 15 minutes. This is of course a big issue.

      By looking at the code, I've seen that the scan of a log is performed once per rule being defined, and then line by line. This is of course very costly in our case.

      Do you have any suggestion about this kind of situation?

      Thanks,
      Damien.

          [JENKINS-32331] Performance problems on scan on huge Jenkins instances

          Damien Coraboeuf created issue -
          Damien Coraboeuf made changes -
          Link New: This issue is related to JENKINS-32685 [ JENKINS-32685 ]
          Damien Coraboeuf made changes -
          Component/s New: token-macro-plugin [ 15832 ]
          Component/s Original: build-failure-analyzer-plugin [ 17224 ]
          Alex Earl made changes -
          Assignee Original: Tomas Westling [ t_westling ] New: Alex Earl [ slide_o_mix ]
          Alex Earl made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 167941 ] New: JNJira + In-Review [ 198315 ]

            slide_o_mix Alex Earl
            damien_coraboeuf Damien Coraboeuf
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: