Do you have some sort of loop that read forwards N entries to get to each value? Ie, each iteration skipped forwards N-1 to get to N. That would produce N^2 reads, or about 9 million.
Jeff On Tue, Jul 3, 2012 at 11:53 AM, Sarang <[email protected]> wrote: > Hello, > > I have an application that was consuming around 11 cents/day of datastore > read operations. Here is a snapshot from historical billing: > > http://gyazo.com/ee441da7686ddff4f3648383e8d7418c > > Today, I wanted to make a small change to a table with around 3000 entries. > I wanted to add another bool field. So I looped over each entry, read each > row, added the boolean field, and saved. I was shocked to note that my app > went over quota and my loop stopped in between. When I looked at the > dashboard, it is showing me 5.8 million datastore read operations. See the > snapshot: > > http://gyazo.com/2dc918ac61c3af295378b8c1a54de77a > > This is absolutely crazy. Can anyone from the App Engine team please explain > this? > > My setup is Django non-rel. The model had only a few fields and I am not > doing anything special in save() method. > > 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/-/p9YMSDN5AEAJ. > 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. -- 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.
