Hi Ikai, you mentioned that queries are faster on HR because they do not guarantee consistency and therefore aren't using transactions. Is it possible to get the same behaviour for some queries at Master/Slave datastore?
Best Regards Philip On Jan 7, 3:13 pm, Matija <[email protected]> wrote: > Thank you. > > I think that we will stay on master/slave version. Now storing one entity > group (two entities) with many indexed properties and several composite > indexes in master/slave datastore is at around 1500 cpu ms and average > latency 300 ms. With 3 times more cost it will be at often over 1000ms > average latency limit, not to mention problem of needed ancestors queries to > present customer stored data in previous request. Maybe with next gen > queries (I assume around may 2011 right before next IO) I will need smaller > composite indexes and cost will be bearable. > > Matija. -- 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.
