F4 Vs F2 Vs F1 I'll bet money, your numbers are right and your conclusion is wrong. F4's have more memory, and more CPU, and more "IO" but the difference I'm 90% certain is that you get a whole VM all to yourself so your neighbors aren't stealing from you. :-) so you get a crap ton more throughput. Watch F4's talk to memcache, It is a whole other beast.
Why didn't you test on an F8? You can do some really, really fun things on an F8. (which isn't really 4.8 GHZ :-) ) You move to an F4 with F8 backends and you will see Appengine through the Rose Colored glasses Brandon does, where the world is always happy, and the numbers never change, and life is all sunshine and rainbows and unicorns . It's all those lousy neighbors who load huge frame works, that Dead Line Exceed on startups cook the CPU and the IO, and then crash only to start up 30 seconds later only to do it again... No losers trying to stuff 129 megs of stuff in to memory along with 64 megs of startup over flowing and going through re-spin up. Nah, co-habitation sucks. Pony up the rent and kick out the room mates, your life will be happier and you will get laid more often too. > -----Original Message----- > From: [email protected] [mailto:google- > [email protected]] On Behalf Of Jeff Schnitzer > Sent: Sunday, June 24, 2012 5:59 PM > To: [email protected] > Subject: Re: [google-appengine] Re: Java instance startup time out of control > > Experiment #2: Bigger better faster frontends > > Using JARed classes, with F2 frontends: > > 19409ms > 18516ms > 17125ms > 18056ms > 17152ms > 18708ms > 28104ms > 16821ms > 18074ms > 16859ms > 18311ms > > Small but noticeable improvement, maybe 10%? > > Same deployment, with F4 frontend: > > 12063ms > 9070ms > 10037ms > 8617ms > 10024ms > 10656ms > 8871ms > 9330ms > 9019ms > 9253ms > > Hot damn! > > I'm not entirely sure how to interpret these results. An F4 is about twice as > fast as an F1. This suggests the problem is significantly computational. > Except that an F2 is more or less the same speed as an F1, which suggests the > problem is almost entirely I/O. > > Maybe F2 instances aren't actually twice the CPU power of an F1? > Maybe F4 instances get some special I/O priority? Anyone want to > speculate? > > Jeff > > On Sun, Jun 24, 2012 at 5:00 PM, Jeff Schnitzer <[email protected]> wrote: > > Experiment #1: JARing my classes. > > > > Times are measured by shutting down instance, hitting a URL, looking > > at request time in logs. Repeat until bored. > > > > First, the "control". My app (sandbox appid), normally deployed > > (classes in WEB-INF/classes): > > > > 21118ms > > 23849ms > > 35995ms > > 20556ms > > 21620ms > > 23718ms > > 34446ms > > 42948ms > > 22487ms > > 32722ms > > 34511ms > > 31883ms > > > > Redeployed, same code but with classes JARed instead of in WEB- > INF/classes: > > > > 19240ms > > 19386ms > > 19912ms > > 27517ms > > 20400ms > > 20483ms > > 20186ms > > 19517ms > > 20352ms > > 19528ms > > 20856ms > > > > What's interesting is that this change didn't improve the best-case > > load times by much, but it almost eliminated the crazy variance. This > > is a huge win. > > > > Conclusion: Use this ant script for deployment: > > > > <target name="deploy"> > > <delete dir="${staging.dir}" /> > > <mkdir dir="${staging.dir}" /> > > > > <copy todir="${staging.dir}"> > > <fileset dir="war"> > > <exclude name="WEB-INF/classes/**" /> > > <exclude > > name="WEB-INF/appengine-generated/**" /> > > </fileset> > > </copy> > > <jar destfile="${staging.dir}/WEB-INF/lib/classes.jar" > > basedir="${classes.dir}" /> > > > > <appcfg action="update" war="${staging.dir}" /> > > </target> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to google- > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
