• Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 7.2.0.CD14
    • Performance, Server
    • None

      The startup time of freshly built WildFly 14.0.0.Final has increased as follows compared to 7.1.0.GA and 7.0.0.GA:

      Difference compared to 7.0.0.GA 7.1.0.GA
      14.0.0.Final standalone.xml on Oracle JDK8u181 34.71822973 % 10.31815117 %
      14.0.0.Final standalone.xml on Oracle JDK11-ea+25 36.2378728 % 11.56255747 %
      14.0.0.Final standalone-full.xml on Oracle JDK8u181 18.31895852 % 6.810011332 %
      14.0.0.Final standalone-full.xml on Oracle JDK11-ea+25 33.5678033 % 20.57559298 %

      In absolutes:

      startup time in ms 7.0.0.GA 7.1.0.GA 14.0.0.Final
      standalone.xml on Oracle JDK8u181 3036 3707.5 4090.045455
      standalone.xml on Oracle JDK11-ea+25     4136.181818
      standalone-full.xml on Oracle JDK8u181 4200.318182 4652.909091 4969.772727
      standalone-full.xml on Oracle JDK11-ea+25     5610.272727

      Startup time is measured as the time difference between first log message (yyyy-mm-dd H:m:s,S INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final) and the last log message (yyyy-mm-dd H:m:s,S INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 14.0.0.Final (WildFly Core 6.0.1.Final) started in <x>ms - Started 345 of 567 services (337 services are lazy, passive or on-demand)).

              andrigmiller Andrig Miller (Inactive)
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: