Need Clarification of App Engine SearchAPI Quota

Question

I'm experimenting with the Search API with appengine, and am consistently running into the "short term burst quota" described in this SO post: quotas on appengine search api for java.

In our use case, we need to delete all documents from an Index, and re-populate the index. We've attacked this by:

Looping through the list and deleting documents
Adding documents through a task queue (1/s) throughput rate

I'm still bumping against this burst limit and I'm wondering if I might have to put a sleep when I delete the documents?

This burst rate is severely limiting us (since we are building these indexes on the fly based on other criteria) and am curious if anyone has any more insight.

score 1 · Accepted Answer · answered Jun 18 '12 at 07:30

1

You should limit the usage using a queue and not sleep (never ever use sleep in AppEngine).
You can request an increase on your quota.

answered Jun 18 '12 at 07:30

Shay Erlichmen

31,691
7
68
87

Thanks Shay for the quick response. I requested more. – user1453956 Jun 18 '12 at 19:15
Shay-- Quick follow-up. I'm assuming that removing documents from an index is also included in the quota count. Do you know if this is correct? – user1453956 Jun 18 '12 at 19:58
@user1453956 remove also has quota, but I don't know if its shared with the indexing quot.a – Shay Erlichmen Jun 18 '12 at 20:17

score 0 · Answer 2 · answered Jul 02 '12 at 07:50

0

I believe that there is a 100 calls per minute quota as well as 20k per day (although the per minute quota may now have been removed).

The best way around this that I have found is with cursors and taskqueues to spread the load.

answered Jul 02 '12 at 07:50

notreadbyhumans

607
9
17

Need Clarification of App Engine SearchAPI Quota

2 Answers2