http://www.morkeleb.com/2009/12/08/appengine-startup-performance-attack-plan-revealed/ Simple design for advanced constructions Mon, 06 Feb 2012 03:50:10 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.morkeleb.com/2009/12/08/appengine-startup-performance-attack-plan-revealed/comment-page-1/#comment-296 Morten Wed, 09 Dec 2009 22:30:02 +0000 http://www.morkeleb.com/?p=913#comment-296 <a href="#comment-295" rel="nofollow">@bendanpa </a> Thanks for the heads up! :) @bendanpa
Thanks for the heads up!

]]> http://www.morkeleb.com/2009/12/08/appengine-startup-performance-attack-plan-revealed/comment-page-1/#comment-295 bendanpa Wed, 09 Dec 2009 22:03:25 +0000 http://www.morkeleb.com/?p=913#comment-295 I just tried that. The total waiting time is still the same. But the app will less likely throw 500 error. Looks like the compile time is not count into the app-engine loading time so even the total wall time is the same the loading time is less. With this feature user will still need to wait for the same time but don't have to reload. Better than nothing. I just tried that. The total waiting time is still the same. But the app will less likely throw 500 error. Looks like the compile time is not count into the app-engine loading time so even the total wall time is the same the loading time is less. With this feature user will still need to wait for the same time but don’t have to reload. Better than nothing.

]]>