On Thu, Feb 12, 2009 at 5:49 AM, Graham Dumpleton < [email protected]> wrote:
> > 2009/2/12 Jannis Leidel <[email protected]>: > > > >> For someone who does not know pinax except that it somehow builds on > >> Django, can someone give me a couple of line summary of what it does. > >> More importantly as far as working out what may be a good > >> configuration, how long do average requests it handles take. Is the > >> nature of the application such that you can have long requests, be it > >> file uploads or some sort of processing, or is every quick and sub > >> second. The length of requests and the number of concurrent requests > >> you get, especially the longer ones, is going to guide how many > >> process/threads you need. > > > > Hi there, > > > > A Pinax developer here. I just wanted to hop in and say that the > > upcoming Pinax release (and current development version) can be used > > in the same way as any other Django based project. I actually doubt > > there is only one good mod_wsgi template for Pinax, since it really > > depends on what core feature a project of a user has. Although we > > provide wsgi scripts (and documentation soon) for the example projects > > included in Pinax we can't foresee what users build with Pinax. > > One guiding rule at least might be, 'do not use Apache embedded mode, > instead use mod_wsgi daemon mode'. > > This is my latest crusade if can find time to blog and write > documentation about it. > > It isn't that embedded mode is broken, but that practically no one > realises that they need to tune Apache MPM settings for embedded mode > to work well for large persistent Python web applications. It is > because this generally never gets done that mod_python has in large > part wrongly got a bad reputation over the years. It wasn't mod_python > that was at fault, but how Apache was setup. > > I have probably been a bit naive over the years in thinking people > knew they had to make changes to the MPM settings for high performance > sites and so haven't made a big deal of it. Getting to the point > though that am getting stick of all the talk of mod_python being so > bad when technically it shouldn't be. There is actually very little > difference between mod_python and mod_wsgi embedded mode and if Apache > not configured properly, you can have many of the same issues that > mod_python has arise with mod_wsgi. > I really love the concept of convention over configuration. Anyone should understand how to setup his server and how to tune and secure it but it doesn't mean that you have to read books just to experiment with a simple application. Users evaluates numerous open source technologies and products in a short period of time so why not make it easy on them and make a simple example that just work. I'm trying to setup a demo that show integration of pinax with our product. I'll might sound like an ignorance but I don't care about embedded mode or daemon mode at this stage. All I wish for at the beginning is specific instructions for using mod_wsgi in production. Once I'll have a working application I'll love to tune it and learn more from personal experience and the community. Coming from the php world, I want to say that python/django/pinax/mod_wsgi are amazing projects. and the above are just my personal thoughts. I'm sorry if it offend anyone or if I'm not the targeted audience of the projects. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
