2

I have loaded 2 Django apps on IIS using isapi-wsgi.

These are both server setups:

  • Windows Server 2003, IIS6 and SQL Server 2005

  • Windows Server 2008 R2, IIS7.5 and SQL Server 2008

The Django apps are completely different from each other.

They both take random periods of time for each requests between 1 and 10 seconds.

This is painfully slow compared to 100ms-500ms of an Apache+mod_wsgi setup, so there must be something wrong.

Any ideas? Would really be great if I could fix this. :)

Solved!

Do not use django-mssql use django-pyodbc instead!!

RadiantHex
  • 24,907
  • 47
  • 148
  • 244

1 Answers1

-3

Install another web server, like apache.

Seriously - IIS sucks on running python wsgi apps. There's not much you can do in that regard.

nosklo
  • 217,122
  • 57
  • 293
  • 297
  • 1
    I wish I could... don't have a choice :( – RadiantHex Nov 16 '10 at 11:48
  • @RadiantHex: You can run a python-only webserver in another port, and configure IIS as a reverse-proxy to forward the requests to this port. I think it would still be faster than using wsgi inside iis. – nosklo Nov 16 '10 at 11:53
  • haha nice, well i don't have a choice if I want to deploy this project within this company... Accenture and IBM have severely locked down any alternatives. – RadiantHex Nov 16 '10 at 11:54
  • @nosklo that sounds like an awesome idea... I could actually use that for one of my projects while the other one is unfortunately off-limits. Any wsgi to suggest, I think that gunicorn is only unix argh – RadiantHex Nov 16 '10 at 11:57
  • 2
    @RadiantHex: If you have a choice of using python, maybe you can run a pure-python wsgi-enabled webserver like cherrypy's one, and then put django on it. Configure IIS to forward requests to it. – nosklo Nov 16 '10 at 11:57
  • 2
    twisted.web.server.wsgi, cherrypy, paster – nosklo Nov 16 '10 at 11:58