Not quite right - I think the "faster" property refers to the fact that reads/writes can happen in parallel (because they're split over multiple machines), not because of the actual geographical location of the servers (not that this wouldn't help as well, but I don't believe GAE currently has support for specifying geographical data location)
I could be wrong though. On 11/02/2009, at 1:43 AM, Big Stu wrote: > >> It also benefits from locality. Entity groups are stored close >> together (needed to make transactions fast), which is why lots of >> small entity groups makes the overall application faster (because >> they >> can be spread out). If you do a bunch of processing on groups of >> entities in a single request then you can put them in a entity group, >> which should make that processing faster because they will be kept >> close. >> >> Dave. > > I don't quite have my head wrapped around the entity group thing > either. The transaction part I get...other benefits I don't quite get > yet. If I were to build an app for managing dollar store inventory or > something like that would I want to make all the data related to a > particular store part of the same entity group? So that the data for > a store in Toronto is part of one group, and the data for Vancouver is > part of another, and then as far as teh datastore and access times are > concerned the storage of the datasets will be best suited to the > geography of the situation? Am I getting this right? > > Thanks. > > Stu > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
