Alexander Boldakov wrote: > Django deployment documentation claims the need of flup as the FastCGI > library. Are there any flup features that Django relies on?
Nothing specific. Flup is recommended because it's pure Python and easier to install. Also documentation *strongly* recommends not to serve media files from Django but to use a separate server instead. This is because serving media from a framework will always be slower and should be avoided. I suspect that even your fix with using more faster FastCGI should still fail you when you get more users. The thing is that you will need a separate process for each download and Django process tends to take about 15-20 MB in memory. Multiply this by user count and you get pretty much memory exhausted for just copying bytes into socket. P.S. I was struggling with similar problem last year and made a 2-part writeup that I think you'll be able to read in Russian: http://softwaremaniacs.org/blog/2006/04/18/controlled-download/ http://softwaremaniacs.org/blog/2006/04/18/controlled-download-2/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
