>> >> Your 5.8M was READ operations anyway. It wasnt't the writing that cost as >> such. > > > That is also strange. Why should it need 5.8m OPs to do 1600 reads?
Well you didnt do 1600 reads. You obvisoully did a lot more. > >> >> >> The other thing, it might even be a red-herring that the the bulk >> update was the issue. Looking at your screenshot, you had a much >> higher request rate for the prev 3 hours. > > > It was the update that was taking all this time. Updates from remote shell > are very slow. So it took 3 hrs for 1000 or so entities that it updated and > consumed 5.8m OPs in the process! Ah, well there you have your answer. The remote shell is not efficent for certain things. Looking back at the code you posted in the thread, looks like reading https://developers.google.com/appengine/articles/remote_api Would be worthwhile, seems like did two mistakes as noted in the Limitations section. An artefact of how the remote_api works, caused all the reads :) > > Regards, > Sarang > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/YxgUMr0fJoEJ. > > 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. -- 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.
