Thanks, this is great. I would be happy to help beta-test this. I'll
contact you via email.

> each request is limited to 10 simultaneous API calls.

I see no limit of "simultaneous [urlfetch] API calls" documented on
the quotas page ( http://code.google.com/appengine/docs/quotas.html ).
I only see a limit of 32000 calls per minute. There is a "simultaneous
dynamic requests" of 30 mentioned on the java runtime page (
http://code.google.com/appengine/docs/java/taskqueue/overview.html ),
but I assume that would not apply to asynchronous URLFetch calls.
Which limit are you referring to, and where is it documented?


On Jan 19, 2:13 pm, Don Schwarz <[email protected]> wrote:
> I just responded to the other thread you pinged, but I'll respond here too
> for completeness.
>
> I've now 
> markedhttp://code.google.com/p/googleappengine/issues/detail?id=1899as
> Acknowledged.  It is currently on schedule to be included in the next
> release.  If you want to help us test it out before that time, please
> contact me privately and I may be able to facilitate that.
>
> However, please note that in Java, as in the current Python API, each
> request is limited to 10 simultaneous API calls.  You cannot "fire off
> several hundred URLFetch calls at a time."  The URLFetch call quota, as with
> all of the non-billable quotas, is designed to protect us from applications
> that are abusing a particular resource.  You shouldn't view them as a
> "right", but more of an additional constraint.
>
> On Mon, Jan 18, 2010 at 9:45 AM, Locke <[email protected]> wrote:
> > We are limited to 32,000 URLFetch calls per minute (that's 533 per
> > second).
>
> > In Python, one could use the .create_rpc() method to fire off several
> > hundred URLFetch calls at a time.
>
> > But in Java, it is absolutely impossible, as far as I can tell, to
> > execute more than a tiny fraction of the allowed amount. To have just
> > two URLFetch calls going at a time, you need to use the TaskQueue. But
> > the TaskQueue has severe limitations. It can have a maximum of 20
> > simultaneous calls (no matter how many users you have). And each of
> > those calls eats into your "simultaneous dynamic request limit" of 30/
> > second (actually less than that, in my experience).
>
> > Has anyone found a way to get Java's URLFetch working at the same
> > level as Python's URLFetch? Or will Java apps never be able to use
> > even small percentage of the allotted URLFetch quotas?
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine for Java" group.
> > To post to this group, send email to
> > [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<google-appengine-java%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine-java?hl=en.
-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" 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-java?hl=en.


Reply via email to