Sorry, My Question is,
When i was use the apache benchmark with 1000 request it automatically
reloading my application, I already introduced the
WSGIScriptReloading Off variable in my apache configuration. in this
not take effect at the moment.
Please Explain is it apache configuration error or other?
here is my apache configuration,
WSGISocketPrefix /tmp/wsgi
NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin [email protected]
WSGIScriptReloading Off
WSGIReloadMechanism Module
WSGIDaemonProcess www.vax.com user=vaxt group=vaxt processes=5
threads=1
WSGIProcessGroup www.vax.com
WSGIApplicationGroup www.vax.com
WSGIScriptAlias / /home/vax/webapps/django/vax/_lib/deploy/
vax.wsgi
#ServerAlias www.www.vax.com www.vax.com
#DocumentRoot /home/vax/webapps/django/vax
ServerName www.vax.com
<Directory /home/vax/webapps/django/vax>
Order allow,deny
Options Indexes
Allow from all
IndexOptions FancyIndexing
</Directory>
ErrorLog /var/log/apache2/error.log
LogLevel info
CustomLog /var/log/http-www.vax.com-access.log combined
ServerSignature On
Alias /media/ /usr/lib/python2.5/site-packages/django/contrib/
admin/media/
<Directory /usr/lib/python2.5/site-packages/django/contrib/
admin/media">
Order allow,deny
Options Indexes
Allow from all
IndexOptions FancyIndexing
</Directory>
SetEnv USER vaxt
SetEnv DJANGO_SETTINGS_MODULE vax.settings
<Directory /home/vax/webapps/django/vax/_lib/deploy>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
On Jan 22, 7:45 pm, Graham Dumpleton <[email protected]>
wrote:
> 2009/1/22 krishna <[email protected]>:
>
>
>
> > hi guys,
>
> > I have bug with "WSGIScriptLoad Off" command, mod_wsgi + apache +
> > django, configured in my system, but its working while we use the
> > browser. me using apache benchmark its took reload wsgi script. What
> > the hell going wrong.
>
> > Please give me your nice guidance for me.
>
> > Advance thanks for all contributers.
>
> Do you mean WSGIScriptReloading directive?
>
> http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIScr...
>
> There is no need to turn it off, the overhead of that check is insignificant.
>
> From your comments I have no idea what you are saying the problem is.
>
> Please explain more clearly what the problem is, or what your expectations
> are.
>
> Also ensure you have read:
>
> http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
> http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode
>
> I am wandering if your expectations don't match what happens.
>
> In particular note that Apache is a multi process web server, so
> multiple copies of your application may have to be loaded depending on
> the configuration you have used. Secondly, by default lazy loading of
> applications is done. If you don't realise this and ensure preloading
> is done, or at least prime your Apache instance first, then benchmarks
> results will look worse than they actually are as you are counting
> cost of loading application.
>
> Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
