Oh, it's MUCH worse than even that. Every single component constructed by your application will get a complete Java stack trace attached to it at the point of construction. Not only does that seriously damage your performance, but this stack trace also takes up space! This is why we warn you about not deploying in development mode on startup.
Martin Voigt-2 wrote: > > Na, nothing "catastrophic" will happen, or else you won't be able to > development your app using development configuration...HOWEVER...the > performance of your app is likely to double when running in deployment > mode, some exceptions won't be visible to the user (i think > component-in-use-check and others), serialization checks won't slow > you down, that kind of stuff. > > If you look at the WebApplication class, you will find lots of getters > like getRequestSettings(), getApplicationSettings() and so forth, from > what I know, development configuration is a defined set of these > configs which sorely focus on helping you while developing, but they > won't help you at all while running in production mode, cos they're > not optimized for that. On the other hand, deployment configuration is > a defined set of these configs which sorely help you getting > performance and "be in production". > > It's like running your app with logging on trace level when in > development...If your app is any good, it may be it won't harm you at > all (we had an app out in production running in development mode for > weeks), but your performance will suffer for sure. > > bw, > Martin > > 2009/4/10 Sam Stainsby <[email protected]>: >> On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote: >> >>> Never *EVER* deploy your application in development mode. Use deployment >>> mode and turn those features you want on. >> >> Just curious - does something catastrophic happen? I'm running a testing >> demo for a client and haven't bothered turning off development mode (I >> assume it is on by default?). It runs fine. >> >> Cheers, >> Sam. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p22981611.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
