hmmm, well Wesley's option B was merely because the batch operations i think. One nice feature about the map reduce is the mutation pool which handles the logic of batching an operation while you yield thru iterations. I guess in a big dataset like yours make sense (the model retrieval vs key only). Anyways, interested case - i'll love to see where it ends :)
On 9 March 2011 19:26, Simon Knott <knott.si...@gmail.com> wrote: > I've been given the impression from these forums that the datastore admin > tool is so expensive for exactly the reason you've stated David - it loads > each entity by key before deletion, whereas deleting purely on keys is much > cheaper CPU-wise as you don't need to bother with the retrieval of the > entire entity to carry out the delete. > > -- > 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. > -- http://about.me/david.mora -- 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.
