On Mar 6, 3:09 pm, ryan <[email protected]> wrote: > db.run_in_transaction() actually adds very little extra overhead. for > read-only transactions, all it adds is a single disk seek to read the > timestamp of the entity group's log header. that read will always be > smaller than any of get(), and more importantly for latency, it's only > a single disk seek, as opposed to queries, which take multiple disk > seeks.
another way to phrase this is, if you only do reads inside db.run_in_transaction(), it effectively already is run_in_snapshot(). it provides the "read a consistent snapshot" functionality with the minimum possible overhead. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
