I'm using 5.2.6. Does the 5.3 beta have better start up optimization?
Is there anything I'm missing to optimize start up time? I refuse to stop using Tapestry (even with the extra start up time) but I also don't want to punish users that have to what for instances to spin up as the app scales. I do know about the Scheduled Task hack (right now we just have always on set on our only pseudo production app [using Google's free $50 credit]). -- View this message in context: http://tapestry.1045711.n5.nabble.com/Optimize-Cold-Start-T5-tp4866408p4868583.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
