First let me say that this is not about production settings for django –

Question

0

Asked: May 23, 20262026-05-23T08:54:51+00:00 2026-05-23T08:54:51+00:00

First let me say that this is not about production settings for django –

0

First let me say that this is not about production settings for django – it’s for local development and testing.

I’m testing out multiple user scenarios, requiring I log in as several different users. I’m logged in as user A using Chrome, and user B using Chrome’s incognito mode, and as user C using Firefox. I’m using “manage.py runserver” to run the dev server.

The first instance with regular Chrome (user A) works well and is fast. The other instances are very slow – perhaps better described as stuck. They sit around doing nothing for 10-30 seconds, and then finally display the page fairly quickly.

While the other browsers are stuck I can go to the first one (user A) and click around and it works well and is fast. In other words only the requests from the other two instances get stuck – the first instance always works well.

The resource that’s slow appears to be the html page, not the static content.

The backend is Django 1.1.1 with SQLite as the database running on OS X 1.6.7 .

Any ideas? Is Chrome doing something special to hog the connection?