So how do you ensure latency is kept low? And what is considered a high latency?
On Mar 11, 1:58 pm, Robert Kluin <[email protected]> wrote: > If you keep latency low you'll get new instances. Those warnings are > left over from previous quotas and limits. You can search the groups > for more info about it. > > Robert > > > > On Fri, Mar 11, 2011 at 05:53, mscwd01 <[email protected]> wrote: > > Hey, > > > I recently finished my app and have since began testing. One of my > > main resources makes 14 RPCs, I have made every effort to decrease CPU > > time I.e. marking properties as unindexed, however I really cannot > > reduce the number of GETs, PUTs and queries that occur in the request. > > > The average CPU times associated with the request today is: > > ms=381 cpu_ms=1192 api_cpu_ms=1122 cpm_usd=0.033597 > > > This does fluctuate and can be less, however it rarely falls low > > enough to have the high CPU warnings removed. > > > I've noticed my app still scales fine, I have about 15 instances > > running whilst testing. > > > So my question is, should I be concerned at the high CPU warnings or > > is it something most people experience? > > > Thanks > > > -- > > 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 > > athttp://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.
