good chat! there are a couple datastore subtleties here that i'd like to expand on:
> [7:37pm] Adhir: marzia:db.put(200 obj) is taking ~2 seconds,is it normal? is > there any way to reduce this > [7:37pm] marzia_google: As my flip-flops will attest to, I am in california > [7:37pm] marzia_google: put on 200 objects? > [7:37pm] Adhir: yes > [7:38pm] marzia_google: puts, in general, are much much much much slower than > reads > [7:38pm] marzia_google: by design > [7:39pm] marzia_google: *plug* > http://sites.google.com/site/io/under-the-covers-of-the-google-app-en... > [7:39pm] pr3d4t0r: marzia_google: Would making all those objects part of the > same > entity group help, though? > [7:39pm] marzia_google: then you would definitely run in to contention issues > [7:39pm] marzia_google: or, most probably > [7:39pm] marzia_google: i would say it's unlikely you would want an entity > group > with 200 entities the spirit here is in the right place, and yes, 2s for a put with 200 entities is not unreasonable. happily, though, entities within a batch put or delete will never cause contention with themselves. batch operations automatically group entities by entity group and write each entity group as a whole. this both avoids contention and decreases overall latency. also, 200 entities per entity group is larger than usual, but isn't problematic on its own. the problem for entity groups is mainly write throughput from concurrent requests, not size. entity groups with tens or even hundreds of thousands of entities may be ok, as long as they're not consistenly being written to by many different requests at once. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
