Hi, I remember some one talking about remote api over-consuming cause of his "retry", so if you are getting some timeout and stuffs like that, the remote api will try again and will consume your quota both times (the success and the timeout).
Maybe this is your case... not sure if my information is correct too... are you using Java? If so, your should try using python bulk upload ( https://developers.google.com/appengine/docs/python/tools/uploadingdata) if it fit in your needs. Hope it helps, cheers. On Sat, Oct 20, 2012 at 10:33 AM, Brian <[email protected]> wrote: > Okay, so with a fresh unused (0%) quota today I tried running my remote > api job again, but first I cut the size of the task down to 1/3 of what it > was previously. On the first run, it consumed 1% of my daily read ops > quota. Encouraged, I ran another batch and within moments it consumed all > 100% of my quota again! What's up with that?! I can not trim my job down to > any smaller chunks than this -- what can I do now to workaround this > problem? > > -- > 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/-/vbz4pmqDfQUJ. > > 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.
