If you want to speedup thing, you should trigger some model loading as early as possible.. (It is too late, if a component calls IModel.getObject() (should return the right value)). Because wicket uses one thread per request you must use an other thread for loading.
This way you could speedup a pageload for one user.. but not for more than one (you have to load it anyway) .. there is a good chance to make it worse. I think you choose a threaded model loading if most other options failed (use a cache, change the query, ...) Mm:) Hendy Irawan <he...@soluvas.com> schrieb: > >Hi friends, > >If I have 5 Wicket (LoadableDetachable)models on a page, will Wicket >load >each model sequentially, or will the 5 models loaded concurrently ? > >We're using different servers for each database connection (MongoDB, >Neo4j, >etc.) so it will be a more effective use to load the models >concurrently. > >Thank you. > > > >-- >View this message in context: >http://apache-wicket.1842946.n4.nabble.com/Are-Wicket-models-loaded-concurrently-tp4655046p4655047.html >Sent from the Users forum mailing list archive at Nabble.com. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >For additional commands, e-mail: users-h...@wicket.apache.org -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
