Have you done any profiling to see where your bottlenecks are? There's a decent set of notes on profiling Django at http://code.djangoproject.com/wiki/ProfilingDjango and an even greater writeup at http://www.rkblog.rk.edu.pl/w/p/django-profiling-hotshot-and-kcachegrind/.
Apache+Mod_Python and Lighttpd+FastCGI have both rendered out (very simple) pages in the sub 100ms range for me. I'd look to the code and see exactly where the bottlenecks are happening. -joe On 3/12/07, Alexander Boldakov <[EMAIL PROTECTED]> wrote: > > > Hello all, > > My django application runs slower under Apache+FastCGI or > Lighttpd+FastCGI than under django development HTTP server. The > approximate times for generating the page are 0.6 vs 1.0 seconds for > FastCGI and development server correspondingly. > > I've tried different combinations of 'prefork' and 'threaded', unix > domain socket and tcp socket, manually/web server started fastcgi > server as described on django FastCGI documentation page, but nothing > helped. > > If you have any idea of solving this problem, i will greatly > appreciate it! > > Django version is 0.95. Python version is 2.4.4. Apache version is > 2.2.3. Flup version is 0.5. > > Alexander Boldakov > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
