Thanks again guys, this is the type of insight I was after. Those charts are rather impressive and in complete contradiction to what I've read elsewhere - the latency seems to be consistently lower.
I think I'll create a new app using the HR datastore and perform some tests, I'm hoping my queries do not have to be changed to avoid returning "stagnant" objects, the docs are rather confusing regarding this issue. On Mar 1, 3:09 pm, bFlood <[email protected]> wrote: > i think he meant that *interaction* with HR is more consistent (e.g. > most requests are in a fixed performance range, whereas there are more > perf spikes with MS). > > nice charts guys, those are helpful! > > On Mar 1, 9:50 am, Geoffrey Spear <[email protected]> wrote: > > > > > > > > > On Mar 1, 8:18 am, Simon Knott <[email protected]> wrote: > > > > What makes you think HR is slower than M/S? This is the case for > > > Puts/Deletes, but for Gets and Querying it's faster and much more > > > consistent. > > > Where do you get "much more consistent" from? The HR datastore is > > eventually consistent; the M/S datastore is strongly consistent. -- 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.
