OK, I think I have figured it out and I'll add it here in case it
saves someone from being as mystified as me:

Chrome sometimes uses multiple http connections.
dev_appserver only uses a single connection.

If you use chrome to access your development server you will very
likely end up with it intermittently hanging, timing out or just
responding really slowly.

The quick fix: don't use chrome on the development server.

link to a source discussing the issue:
https://groups.google.com/group/google-appengine-python/browse_thread/thread/619d46a1e3d08c67

Best,
Alex.

On Mar 30, 1:53 am, "Jason (spot) Brower" <[email protected]> wrote:
> Do you have an internet connection when you are working locally? If not it
> may be pausing because it is looking some file that is not accessable and
> needs to time out. Is you app somewhere that we could test it?
> On 29 Mar 2011 22:45, "Chris" <[email protected]> wrote:
>
> > Have you tried running it with the profiler and viewing a log for one
> > page request?
>
> http://groups.google.com/group/web2py/browse_thread/thread/8e38fc1c17...
>
>
>
>
>
>
>
>
>
> > On Mar 29, 1:03 pm, Alex Darlington <[email protected]> wrote:
> > > Hi,
> > > I am using web2py for google app engine and doing development on
> > > windows 7 and XP machines.
> > > I recently changed some code to start using the blob store (in case
> > > this is relevant?) and now have a pretty unusable development
> > > environment.
>
> > > The first time I visit a page it takes over a minute to appear. If I
> > > go back to it, it usually appears instantly.
> > > If anything changes, the page will once again take over a minute to
> > > load. Also after a certain amount of time/visits the response will
> > > slow down again.
>
> > > The problems do not appear when the code is running on Google's
> > > servers.
>
> > > I'm at a bit of a loss as to how to work out what is causing the slow
> > > response. This is my first go with python/web2py/appengine (all of
> > > them).
>
> > > Any suggestions gratefully received!
>
> > > Thanks,
> > > Alex.

Reply via email to