Yes, we are still using the M/S datastore. We feel that we are not offering mission critical services. These services don't require the HRD level availability. HRD db read/write/store all costs more. I know we could save some CPU hours by using Python 2.7 concurrency feature if we move over to HRD. There is loss and there is gain. Overall, we don't see our cost will reduce by moving M/S to HRD. That is why we are reluctant to make the move.
I have always wondered why GAE doesn't extend Python 2.7 support to M/S. It doesn't seem there is any particular technical blocker. Maybe I'm wrong. In this random latency case, I again wonder why GAE doesn't plan to fix for M/S servers. Is the plan to completely phase out M/S servers in some near future? On Wed, Dec 14, 2011 at 1:27 AM, Kenneth <[email protected]>wrote: > Are you using the old MS datastore or the HR datastore? If you're using MS > then pretty much anything to do with the datastore is totally random, so > expect random latency increases which result in higher instance counts and > thus higher cost to you, randomly of course. Google will not be fixing > these so move to the hr datastore when you can. > > -- > 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/-/PsCn4-PDjvUJ. > > 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.
