We migrated our app to the HRD last night. With 4 GB of data quota in around 2M entities it took 20-30 minutes. On the new app, we are seeing response times at about 1% of the MS app - 100 times faster. Our app was read only for less than three seconds - enough to affect 10 requests from 2 users.
We decided to do this without a very thorough testing because the app was broken across all of our users on M/S, and will only break in a small percentage of users on HRD. When it does break, it will be pretty harmless, and we expect to fix the inconsistency problems by the end of today. We just could not wait until Monday for a possible fix for the MS app. If you've got a similar setup or similar needs, I recommend a hastier-than-usual switch. Just watch out for the email limits~ On Tue, Mar 13, 2012 at 9:04 AM, Johan Euphrosine <[email protected]> wrote: > If you are not using the datastore it should be trivial to move your > application to the new HRD infrastructure. > > If you don't need the same appid, just create a new HRD application and > deploy your code on it. > > If you need the same appid, use the self migration tool: > https://appengine.google.com/migrating?app_id=<your application id> > > Feel free to open a production ticket if you need any assistance migrating > your application: > > http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue > > > On Tue, Mar 13, 2012 at 12:44 PM, charisl <[email protected]> wrote: > >> Hello Ikai >> >> our app is *betscoreslive*. In our settings master/slave replication is >> activated but we are NOT using the datastore at all and we have been >> experiencing the DeadlineExceedExceptions and increased instance number >> mentioned by the rest of the people in the discussion. Our app is only >> using memcache. >> >> Normal operation >> during traffic peaks: instances ~25, ~45 requests/second and QPS > 1 >> >> Now we observe: 12 instances doing nth with ~2 requests/second and QPS 0.2 >> We had the Deadline exceptions since one week now with small periods of >> normal operation. During the problematic periods, our app is pretty >> unresponsive. >> >> Will the announced maintenance for master/slave apps will solve the issue >> for our app as well? >> >> thanks in advance >> >> Charis >> >> On Friday, March 9, 2012 9:15:35 PM UTC+2, Ikai Lan wrote: >>> >>> Hey everyone, >>> >>> Here are a few things that will help: >>> >>> 1. Application IDs (<--- if you have nothing else, at least provide this) >>> 2. What is your QPS? >>> 3. What % of your requests are errors? >>> >>> -- >>> Ikai Lan >>> Developer Programs Engineer, Google App Engine >>> plus.ikailan.com >>> >>> >>> >>> On Fri, Mar 9, 2012 at 7:24 AM, Ronoaldo José de Lana Pereira < >>> [email protected].**br <[email protected]>>wrote: >>> >>>> +1 for seeing the same problems on my app. >>>> >>>> It started to be worse after maintenance on March 7. >>>> >>>> Em sexta-feira, 9 de março de 2012 08h33min36s UTC-3, Nikolai escreveu: >>>> >>>>> +1 >>>>> we had to move to our backup systems. Everything is full of 500 errors >>>>> or hardcore latency. >>>>> Most of the 500 errors we see aren't even logged so this seems to be a >>>>> goole problem one abstraction layer above the app. >>>>> >>>>> And yes - sometimes we have got the same feeling, that we are the only >>>>> ones that use appengine in a production setting. You are not alone ;) >>>>> >>>>> regards, >>>>> nikolai >>>>> >>>>> Am Dienstag, 6. März 2012 22:17:37 UTC+1 schrieb Adam Sherman: >>>>>> >>>>>> Am I the only one seeing short duration outages? They are being >>>>>> reflected at: >>>>>> >>>>>> http://code.google.com/status/****appengine<http://code.google.com/status/appengine> >>>>>> >>>>>> But I don't see anyone else complaining anywhere, so it makes me >>>>>> worried. >>>>>> >>>>>> A. >>>>>> >>>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To view this discussion on the web visit https://groups.google.com/d/** >>>> msg/google-appengine/-/**yixu1yAlMs4J<https://groups.google.com/d/msg/google-appengine/-/yixu1yAlMs4J> >>>> . >>>> >>>> To post to this group, send email to google-appengine@googlegroups.** >>>> com <[email protected]>. >>>> To unsubscribe from this group, send email to >>>> google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]> >>>> . >>>> For more options, visit this group at http://groups.google.com/** >>>> group/google-appengine?hl=en<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 view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/W1KVvW7v-SEJ. >> >> 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. >> > > > > -- > Johan Euphrosine (proppy) > Developer Programs Engineer > Google Developer Relations > > -- > 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. > -- 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.
