Daniel keep in mind that you data is still co-hosted with dozens or 
hundreds on other apps on the same physical node. That is what makes 
performance volatile not M/S vs HRD. HRD did solve the problem for writes 
somewhat but not for reads. Fundamentally if an app which runs on the same 
node is really active *your* app's performance will suffer. So it is dump 
luck. Since you got a new appid when migrating you got new "neighbors" so 
to speak - apps which share bigtable node with your app.

-- 
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/-/7NEAU3WOrG8J.
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.

Reply via email to