read this : http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
On Thu, Jan 7, 2010 at 1:18 PM, bharath venkatesh < [email protected]> wrote: > Hi Jason, > > Thanks for reply. > > >Why don't you give it a try, and post back if you run into trouble. By > the way, you may want to consider testing >with a 1-file plain WSGI > application to verify that mod_wsgi is working before cluttering it up with > Django. > > sorry If I was not clear in my earlier post .I am quite aware of the WSGI > configuration and I had already run Django application with wsgi in daemon > mode in apache worker mpm in test machine and it was working with out any > issues . Also most of the places (which I read )it was mentioned that wsgi > daemon mode must be used with apache worker mpm . But I came across post > http://stackoverflow.com/questions/1475960/performance-of-concurrency-in-django-apache2-prefork-modwsgi-what-am-i-doing/1481023#1481023,where > the last comment(made by Graham ) said > *"Even if you do still have to run single threaded prefork MPM, the > mod_wsgi daemon processes can still be multithreaded" , *so I was quite > eager to know that if it is possible to use mod_wsgi in daemon mode in > apache prefork mpm (also be multi threaded ) , would it work the same way as > it would in apache worker mpm ? > > thanks, > Bharath > > > > > > > > > On Thu, Jan 7, 2010 at 6:56 AM, Jason Garber <[email protected]> wrote: > >> Hi Bharath, >> >> I'll quote >> http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIDaemonProcess >> >> > When distinct daemon processes are enabled and used, the process is >> >> > >> dedicated to mod_wsgi and the only thing that the processes do is run >> >> > >> the WSGI applications assigned to that process group. Any other Apache >> >> > >> modules such as PHP or activities such as serving up static files >> continue >> >> > >> to be run in the standard Apache child processes. >> >> > >> Note that having denoted that daemon processes should be created by >> >> > >> using the WSGIDaemonProcess directive, the WSGIProcessGroup >> >> > >> directive still needs to be used to delegate specific WSGI applications >> >> > >> to execute within those daemon processes. >> >> > >> Also note that the name of the daemon process group must be unique >> >> > >> for the whole server. That is, it is not possible to use the same daemon >> >> > >> process group name in different virtual hosts. >> >> By judicious use of WSGIDaemonProcess and WSGIProcessGroup, you should be >> able to keep your currently running configuration, but ADD additional >> VirtualHosts that are deligated to specific daemon processes, where they >> will not affect each other. >> >> Why don't you give it a try, and post back if you run into trouble. By >> the way, you may want to consider testing with a 1-file plain WSGI >> application to verify that mod_wsgi is working before cluttering it up with >> Django. >> >> Good luck, >> Jason Garber >> >> >> On Wed, Jan 6, 2010 at 9:53 AM, bharath venkatesh < >> [email protected]> wrote: >> >>> Hi, >>> >>> is it possible to run mod_wsgi in multi threaded daemon mode in >>> apache prefork MPM. Apparently we are running mod_php and muiltple django >>> application that use django version 0.97 which is not thread safe out of >>> that we upgraded only one django application to newest version due some >>> reasons other django applications could not be upgraded. As in the post >>> http://stackoverflow.com/questions/1475960/performance-of-concurrency-in-django-apache2-prefork-modwsgi-what-am-i-doing/1481023#1481023,where >>> the last comment said >>> *"Even if you do still have to run single threaded prefork MPM, the >>> mod_wsgi daemon processes can still be multithreaded" >>> >>> *so is it possible to run one django application which is upgraded >>> (which is thread safe) in mod_wsgi multi threaded daemon mode and to run >>> other django applications (which is not thread safe) in mod_wsgi embedded >>> mode and leave mod_php as it is ? >>> >>> if yes, what are the things we have to consider in doing so and is there >>> any problem that may arise in doing so ? >>> >>> Thanks in Advance, >>> Bharath >>> * >>> * >>> >>> -- >>> 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]<modwsgi%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/modwsgi?hl=en. >>> >>> >> >> -- >> 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]<modwsgi%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/modwsgi?hl=en. >> >> > > -- > 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]<modwsgi%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- [+]-------------------------------{+} {+}------------------------------[+] -=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-= Eric_yang -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==--
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.
