I should probably mention that the URLFetches are going to an external 
resource, not my own app. 

On Thursday, May 23, 2013 10:45:19 AM UTC-7, John Wheeler wrote:
>
> Hello,
>
> I am using the new python development server with the app engine 1.8.0 
> release. The Google Code page for said dev server here:
>
> https://code.google.com/p/appengine-devappserver2-experiment/
>
> states
>
>    - Multithreaded serving for *better* *performance* for complex 
>    applications and more correct semantics e.g. accessing your own 
> application 
>    through urlfetch no longer deadlocks.
>
> However, and I don't know if I'm getting the meaning mixed up, but it 
> doesn't appear like it can run URLFetches concurrently with one another.
>
> I have a task the fans-out a whole bunch of URLFetches, and they process 
> one at a time, very slowly in the new development server. I want them to 
> process at the same time.
>
> Furthermore it appears each one starts a new instance because in the dev 
> admin console, I refresh the page and there's only one instance listed with 
> a request count of 1 at any given time. This is in the new dev server that 
> ships with the SDK - this doesn't happen if I clone the Google repo above 
> and run from that--but the URLFetches still process serially in either case.
>
> John
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to