On Tue, Oct 8, 2013 at 12:24 PM, James Gilliam <[email protected]> wrote:

> Memcache continues to perform poorly; I suspect they are making many
> changes to it.
>
> Saturday was awful -- aggressively purging memcache, Sunday was better,
> Monday was worse than Sunday.
>
> At this point, not sure what to do ... are we dealing with just code
> instability or some fundamental change?
>
>

Can you try changing the instance class size to a larger class ( ie from F1
to F2 ) and then back again? Sometimes applications get stuck with
"damaged" instances and experience reduced reliability. Changing the
instance class size forces the scheduler to reallocate new instances, which
will hopefully open on a more reliable machine/different place within the
physical Google infrastructure.


-----------------
-Vinny P
Technology & Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to