[wildfly-dev] Reducing Startup Time and Footprint with AppCDS

David Lloyd david.lloyd at redhat.com
Mon Feb 19 09:05:52 EST 2018


On Sun, Feb 18, 2018 at 5:12 AM, Philippe Marschall <kustos at gmx.net> wrote:
> Hello
>
> There has been a lot of talk on this list about how startup time and
> footprint of WildFly can be reduced even further. I have experimented
> with AppCDS and the first results are encouraging.

Cool!

> [...]
> I checked the startup time reported by an "empty" WildFly 11. I realize
> this is not the most scientific way. The startup time went down from
> about 2000ms to about 1500ms or by about 25%. I did not have a look at
> the memory savings when running multiple WildFly versions is parallel.
>
> One thing I noted is that the Xerces classes should probably be
> recompiled with bytecode major version 49 (Java 1.5) or later, otherwise
> they can not be processed by AppCDS.
>
> Unfortunately AppCDS is quite hard to use, I don't know if the WildFly
> project can somehow help to make this easier. One option would be to
> ship a class list file but I don't know how portable that is. Also as
> WildFly services are lazy it only a fraction of the required classes may
> be in there.

What about simply adding *all* the classes (I think there are about
78,000 of them) to AppCDS?

-- 
- DML


More information about the wildfly-dev mailing list