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

Improve performance of parsers for long log files

    XMLWordPrintable

Details

    Description

      Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

      Here are some performance results on a log file of 840 lines:

      AcuCobol Compiler: 2439ms
      Ada Compiler (gnat): 21ms
      Buckminster Compiler: 12ms
      Coolflux DSP Compiler: 959ms
      Doxygen: 18ms
      Eclipse Java Compiler: 19ms
      Erlang Compiler: 11ms
      Flex SDK Compilers (compc & mxmlc): 113ms
      GNU compiler (gcc): 710ms
      GNU compiler 4 (gcc): 19ms
      GNU compiler 4 (ld): 700ms
      IAR compiler (C/C++): 14ms
      Intel compiler: 977ms
      Java Compiler: 137ms
      JavaDoc: 17ms
      MSBuild: 4491ms
      Oracle Invalids: 53ms
      PC-Lint: 4678ms
      PHP Runtime Warning: 1569ms
      Perforce Compiler: 2531ms
      Robocopy (please use /V in your commands!): 1733ms
      SUN C++ Compiler: 14ms
      Texas Instruments Code Composer Studio (C/C++): 3ms

      Here are the results after the optimzation:

      AcuCobol Compiler: 15ms
      Ada Compiler (gnat): 27ms
      Buckminster Compiler: 19ms
      Coolflux DSP Compiler: 2ms
      Doxygen: 18ms
      Eclipse Java Compiler: 29ms
      Erlang Compiler: 24ms
      Flex SDK Compilers (compc & mxmlc): 6ms
      GNU compiler (gcc): 96ms
      GNU compiler 4 (gcc): 20ms
      GNU compiler 4 (ld): 68ms
      IAR compiler (C/C++): 19ms
      Intel compiler: 5ms
      Java Compiler: 53ms
      JavaDoc: 13ms
      MSBuild: 72ms
      Oracle Invalids: 6ms
      PC-Lint: 99ms
      PHP Runtime Warning: 2ms
      Perforce Compiler: 3ms
      Robocopy (please use /V in your commands!): 2ms
      SUN C++ Compiler: 4ms
      Texas Instruments Code Composer Studio (C/C++): 3ms

      Attachments

        Activity

          drulli Ulli Hafner created issue -
          drulli Ulli Hafner made changes -
          Field Original Value New Value
          Description Currently, the performance when parsing the log files is poor. Maybe we should use another regexp library. Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 1894ms
          Ada Compiler (gnat): 54ms
          Buckminster Compiler: 15ms
          Eclipse Java Compiler: 43ms
          Erlang Compiler: 35ms
          GNU compiler (gcc): 351ms
          IAR compiler (C/C++): 8ms
          Intel compiler: 317ms
          Java Compiler: 52ms
          JavaDoc: 10ms
          MSBuild: 1451ms
          Oracle Invalids: 24ms
          PC-Lint: 1371ms
          SUN C++ Compiler: 6ms
          Texas Instruments Code Composer Studio (C/C++): 2ms
          drulli Ulli Hafner made changes -
          Description Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 1894ms
          Ada Compiler (gnat): 54ms
          Buckminster Compiler: 15ms
          Eclipse Java Compiler: 43ms
          Erlang Compiler: 35ms
          GNU compiler (gcc): 351ms
          IAR compiler (C/C++): 8ms
          Intel compiler: 317ms
          Java Compiler: 52ms
          JavaDoc: 10ms
          MSBuild: 1451ms
          Oracle Invalids: 24ms
          PC-Lint: 1371ms
          SUN C++ Compiler: 6ms
          Texas Instruments Code Composer Studio (C/C++): 2ms
          Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 2439ms
          Ada Compiler (gnat): 21ms
          Buckminster Compiler: 12ms
          Coolflux DSP Compiler: 959ms
          Doxygen: 18ms
          Eclipse Java Compiler: 19ms
          Erlang Compiler: 11ms
          Flex SDK Compilers (compc & mxmlc): 113ms
          GNU compiler (gcc): 710ms
          GNU compiler 4 (gcc): 19ms
          GNU compiler 4 (ld): 700ms
          IAR compiler (C/C++): 14ms
          Intel compiler: 977ms
          Java Compiler: 137ms
          JavaDoc: 17ms
          MSBuild: 4491ms
          Oracle Invalids: 53ms
          PC-Lint: 4678ms
          PHP Runtime Warning: 1569ms
          Perforce Compiler: 2531ms
          Robocopy (please use /V in your commands!): 1733ms
          SUN C++ Compiler: 14ms
          Texas Instruments Code Composer Studio (C/C++): 3ms
          drulli Ulli Hafner made changes -
          Description Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 2439ms
          Ada Compiler (gnat): 21ms
          Buckminster Compiler: 12ms
          Coolflux DSP Compiler: 959ms
          Doxygen: 18ms
          Eclipse Java Compiler: 19ms
          Erlang Compiler: 11ms
          Flex SDK Compilers (compc & mxmlc): 113ms
          GNU compiler (gcc): 710ms
          GNU compiler 4 (gcc): 19ms
          GNU compiler 4 (ld): 700ms
          IAR compiler (C/C++): 14ms
          Intel compiler: 977ms
          Java Compiler: 137ms
          JavaDoc: 17ms
          MSBuild: 4491ms
          Oracle Invalids: 53ms
          PC-Lint: 4678ms
          PHP Runtime Warning: 1569ms
          Perforce Compiler: 2531ms
          Robocopy (please use /V in your commands!): 1733ms
          SUN C++ Compiler: 14ms
          Texas Instruments Code Composer Studio (C/C++): 3ms
          Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 2439ms
          Ada Compiler (gnat): 21ms
          Buckminster Compiler: 12ms
          Coolflux DSP Compiler: 959ms
          Doxygen: 18ms
          Eclipse Java Compiler: 19ms
          Erlang Compiler: 11ms
          Flex SDK Compilers (compc & mxmlc): 113ms
          GNU compiler (gcc): 710ms
          GNU compiler 4 (gcc): 19ms
          GNU compiler 4 (ld): 700ms
          IAR compiler (C/C++): 14ms
          Intel compiler: 977ms
          Java Compiler: 137ms
          JavaDoc: 17ms
          MSBuild: 4491ms
          Oracle Invalids: 53ms
          PC-Lint: 4678ms
          PHP Runtime Warning: 1569ms
          Perforce Compiler: 2531ms
          Robocopy (please use /V in your commands!): 1733ms
          SUN C++ Compiler: 14ms
          Texas Instruments Code Composer Studio (C/C++): 3ms

          Here are the results after the optimzation:

          AcuCobol Compiler: 37ms
          Ada Compiler (gnat): 95ms
          Buckminster Compiler: 51ms
          Coolflux DSP Compiler: 4ms
          Doxygen: 32ms
          Eclipse Java Compiler: 66ms
          Erlang Compiler: 86ms
          Flex SDK Compilers (compc & mxmlc): 19ms
          GNU compiler (gcc): 325ms
          GNU compiler 4 (gcc): 130ms
          GNU compiler 4 (ld): 277ms
          IAR compiler (C/C++): 99ms
          Intel compiler: 26ms
          Java Compiler: 165ms
          JavaDoc: 67ms
          MSBuild: 332ms
          Oracle Invalids: 10ms
          PC-Lint: 333ms
          PHP Runtime Warning: 14ms
          Perforce Compiler: 8ms
          Robocopy (please use /V in your commands!): 15ms
          SUN C++ Compiler: 10ms
          Texas Instruments Code Composer Studio (C/C++): 13ms
          drulli Ulli Hafner made changes -
          Description Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 2439ms
          Ada Compiler (gnat): 21ms
          Buckminster Compiler: 12ms
          Coolflux DSP Compiler: 959ms
          Doxygen: 18ms
          Eclipse Java Compiler: 19ms
          Erlang Compiler: 11ms
          Flex SDK Compilers (compc & mxmlc): 113ms
          GNU compiler (gcc): 710ms
          GNU compiler 4 (gcc): 19ms
          GNU compiler 4 (ld): 700ms
          IAR compiler (C/C++): 14ms
          Intel compiler: 977ms
          Java Compiler: 137ms
          JavaDoc: 17ms
          MSBuild: 4491ms
          Oracle Invalids: 53ms
          PC-Lint: 4678ms
          PHP Runtime Warning: 1569ms
          Perforce Compiler: 2531ms
          Robocopy (please use /V in your commands!): 1733ms
          SUN C++ Compiler: 14ms
          Texas Instruments Code Composer Studio (C/C++): 3ms

          Here are the results after the optimzation:

          AcuCobol Compiler: 37ms
          Ada Compiler (gnat): 95ms
          Buckminster Compiler: 51ms
          Coolflux DSP Compiler: 4ms
          Doxygen: 32ms
          Eclipse Java Compiler: 66ms
          Erlang Compiler: 86ms
          Flex SDK Compilers (compc & mxmlc): 19ms
          GNU compiler (gcc): 325ms
          GNU compiler 4 (gcc): 130ms
          GNU compiler 4 (ld): 277ms
          IAR compiler (C/C++): 99ms
          Intel compiler: 26ms
          Java Compiler: 165ms
          JavaDoc: 67ms
          MSBuild: 332ms
          Oracle Invalids: 10ms
          PC-Lint: 333ms
          PHP Runtime Warning: 14ms
          Perforce Compiler: 8ms
          Robocopy (please use /V in your commands!): 15ms
          SUN C++ Compiler: 10ms
          Texas Instruments Code Composer Studio (C/C++): 13ms
          Currently, the performance when parsing the log files is poor for some parsers. Maybe we should use another regexp library or strip off some text from the log before starting the parser.

          Here are some performance results on a log file of 840 lines:

          AcuCobol Compiler: 2439ms
          Ada Compiler (gnat): 21ms
          Buckminster Compiler: 12ms
          Coolflux DSP Compiler: 959ms
          Doxygen: 18ms
          Eclipse Java Compiler: 19ms
          Erlang Compiler: 11ms
          Flex SDK Compilers (compc & mxmlc): 113ms
          GNU compiler (gcc): 710ms
          GNU compiler 4 (gcc): 19ms
          GNU compiler 4 (ld): 700ms
          IAR compiler (C/C++): 14ms
          Intel compiler: 977ms
          Java Compiler: 137ms
          JavaDoc: 17ms
          MSBuild: 4491ms
          Oracle Invalids: 53ms
          PC-Lint: 4678ms
          PHP Runtime Warning: 1569ms
          Perforce Compiler: 2531ms
          Robocopy (please use /V in your commands!): 1733ms
          SUN C++ Compiler: 14ms
          Texas Instruments Code Composer Studio (C/C++): 3ms

          Here are the results after the optimzation:

          AcuCobol Compiler: 15ms
          Ada Compiler (gnat): 27ms
          Buckminster Compiler: 19ms
          Coolflux DSP Compiler: 2ms
          Doxygen: 18ms
          Eclipse Java Compiler: 29ms
          Erlang Compiler: 24ms
          Flex SDK Compilers (compc & mxmlc): 6ms
          GNU compiler (gcc): 96ms
          GNU compiler 4 (gcc): 20ms
          GNU compiler 4 (ld): 68ms
          IAR compiler (C/C++): 19ms
          Intel compiler: 5ms
          Java Compiler: 53ms
          JavaDoc: 13ms
          MSBuild: 72ms
          Oracle Invalids: 6ms
          PC-Lint: 99ms
          PHP Runtime Warning: 2ms
          Perforce Compiler: 3ms
          Robocopy (please use /V in your commands!): 2ms
          SUN C++ Compiler: 4ms
          Texas Instruments Code Composer Studio (C/C++): 3ms
          drulli Ulli Hafner made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135274 ] JNJira + In-Review [ 203374 ]

          People

            drulli Ulli Hafner
            drulli Ulli Hafner
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: