> > > Exactly. You only do it when you are writing anyway. > We may not be writing them.. that is the problem!
> > > > > Bottom line is, even if we had to write those 1600 numbers, why should > it > > cost 5.8 million OPs? If we signup 1600 users in a day, each with one > entry > > in the DB, then we'll use up all our quota! > > > 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? > > 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! 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.
