2008/12/16 xerophyte <[email protected]>:
>
> Hey,
> I have slow loading with trac + wsgi configuration, its takes forever
> to load in the browser, but it works fine after it loaded.
>
> Just wondering if somebody tell me know if i am doing something wrong
> with mod_wsgi configuration. When i run the trac with tracd it works
> fine
>
> could somebody let me know what am i doing it wrong
The WSGI script file is only loaded by default when first request
targeting that script is received. This means that for a heavy weight
framework with high startup cost you will see a delay.
You can avoid some of this startup cost, depending on the
application/framework, by preloading the WSGI script file when process
starts up.
For how to do this, see after have detailed other corrections to your
configuration below.
> configuration
>
> WSGIDaemonProcess ops.wsgi user=trac group=tracgroup processes=3
> threads=10
> WSGIScriptAlias / /svn/trac/project/www/trac.wsgi
>
> <Directory /svn/trac/project/www>
> WSGIApplicationGroup trac
For Trac, using this value may cause problems. For Trac you should
force it to run in first interpreter created by Python. This is done
by using:
WSGIApplicationGroup %{GLOBAL}
> WSGIProcessGroup trac.wsgi
This would appear to be wrong. It should match name of daemon process
group. In your case should be:
WSGIProcessGroup ops.wsgi
That being the first argument to WSGIDaemonProcess.
That you had this wrong may have caused initial startup times to be
much worse as it would have had to do it for each Apache worker
process as it wouldn't have been running in daemon process as you
expected. Since you are using worker MPM, it may not have made that
much difference, but if using prefork MPM it would have as typically a
lot more worker processes in that case.
Back to preloading, use:
WSGIImportScript /svn/trac/project/www/trac.wsgi
process-group=ops.wsgi application-group=%{GLOBAL}
That is, name the WSGI script file and the process group/application
group to preload it into.
Because of deficiency in mod_wsgi, this will need to be outside of the
VirtualHost container. This issue logged at:
http://code.google.com/p/modwsgi/issues/detail?id=110
Graham
>
> Linux Debian etch
> ii apache-common 1.3.34-4.1+etch1
> support files for all Apache webservers
> ii apache2 2.2.3-4+etch6
> Next generation, scalable, extendable web se
> ii apache2-mpm-worker 2.2.3-4+etch6
> High speed threaded model for Apache HTTPD 2
> ii apache2-utils 2.2.3-4+etch6
> utility programs for webservers
> ii apache2.2-common 2.2.3-4+etch6
> Next generation, scalable, extendable web se
> ii libapache-mod-ldap 1.8-2
> Apache authentication via LDAP directory
> ii libapache2-mod-auth-pam 1.1.1-6.1
> module for Apache2 which authenticate using
> ii libapache2-mod-auth-sys-group 1.1.1-6.1
> Module for Apache2 which checks user against
> ii libapache2-mod-wsgi 2.3-1~bpo40+1
> Python WSGI adapter module for Apache
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
