-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an app that needs to touch a lot of objects every time the user does anything.
Right now I've got code that lazily pulls the needed objects out of the datastore as they're accessed, one at a time, and then once finished does a bulk put to save them back again (using DataStoreService.put(Iterable<Entity>)). The problem is that the app is taking 8-10 seconds per request (!), which is clearly unacceptable... Is it worth my while changing it to load *all* my objects into memory in a single DataStoreService.get(Iterable<Key>) request? That way I'm loading more objects than I need, but only doing a single round-trip to the datastore. Is this a net win? What kind of data transfer bandwidth do I get from the datastore? How does this compare to the time taken for a single round-trip? Also, from the quota perspective, do the bulk get and put requests count as a single datastore API use, or am I billed for each entity transferred? - -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ "People who think they know everything really annoy those of us who │ know we don't." --- Bjarne Stroustrup -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKizDDf9E0noFvlzgRAmVyAJ4wg/kJBtbRa4FlEh+/jrLnFZr/WwCgn+32 j9kypp39zIz+NdwAP5L0OE4= =Wowz -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
