Hi, You should see what is slow first. The best is to use a profiler. If you don't have experience with profilers then just print something in YourApplication#init() method - before calling super.init(), after calling it, and then around every resource initialization, e.g. DB setup, etc.
On Tue, Oct 29, 2024 at 1:06 PM <s...@stantastic.nl.invalid> wrote: > Hi there, > > I am looking for some advise on how to improve the startup time of my > Wicket webapp. The company I work for has developed an appliance that > frequently needs to be reset when there are configuration changes. The > web interface of this appliance is a wicket web application that runs on > Apache Tomcat 9. > > Sadly our hardware isn't very high end. It has a Celeron processor and 2 > or 4GB of RAM. This makes starting the device itself slow (several > seconds), and starting the Wicket app even slower (20+ seconds for > Tomcat to load). > > I was wondering if anyone could give me some pointers on how to make > some gains here. I have looked into some Tomcat optimization guides, and > have gained a bit by turning off scanning JAR files but nothing > spectacular. I have also turned off Wicket's > PackageStringResourceLoader, which seems to help a bit. but again: no > huge gains. > > If anyone could give me some hints, it would be much appreciated. > > Thanks. > > Stan
