Anything in wicket can be preloaded, but as premature optimization is evil, you should profile your application.
If you do not have debug access to a real/simulated environment then the least you can do is make your own thread logger to log what the threads are doing. ** Martin ma 2. tammik. 2023 klo 3.19 Anna Eileen (shengchehs...@gmail.com) kirjoitti: > Hello > > Would you please describe your web application components? Database ? > What services ran on the device? > > > From: s...@stantastic.nl <s...@stantastic.nl> > Date: Monday, January 2, 2023 at 5:23 AM > To: users@wicket.apache.org <users@wicket.apache.org> > Subject: Wicket on low end hardware > > > Hi, > > My use case for Wicket is a quite unconventional one. I use it as the > framework for the web interface of an appliance that runs on low end > hardware. The appliance doesn't have gigabytes of memory to waste or > tens of CPU cores. It's more like Celeron powered hardware with maybe > one or two gigabytes of RAM. > > I general this all works and customers are happy once the device is > running. But I find that deployment is quite slow, and so are the first > couple of page loads of the day. Just to be clear: I cannot really claim > that my performance problems are all Wicket related. They may be, but > they probably also are down to other underlying issues. A badly > optimized database, or a badly configured servlet container come to > mind... > > However, I was wondering if anyone has experience in using Wicket on low > end hardware. I would be very interested in how to optimize for this. > > Thanks, > > Stan >
