thanks buddy! for the insight. let me see whats available with my host ;) On Fri, Dec 30, 2011 at 1:32 AM, spiffytech <[email protected]> wrote:
> If I read the state dump correctly, your site is running over CGI, the > slowest possible way to host a Python website. CGI starts a new > process for each request. This is fine for PHP, since the PHP runtime > starts up very quickly. The Python virtual machine, however, starts up > much more slowly. > > I expect most of your performance hit comes from the web server > starting the whole Python interpreter and web2py program fresh for > each page load. If you have the option, switch to _any_ other server > interface protocol (WSGI is most preferred, then mod_python, then > fastcgi). These all start the Python process when the web server > starts and let the existing process handle new requests as they come > in. > > > On Dec 29, 5:12 am, Zen Master <[email protected]> wrote: > > Hi guys, i installed web2py on my shared hosting a/c and configured a > > index.py as CGI/FASTCGI gateway and then configured .htaccess to send all > > traffice thru this index.py.... but it seems to be working slower than > PHP. > > i complied the app and set migrate=False to disable migration and tried > > again but still seems to be lagging behind PHP. Is is it common or there > > are some special steps or tips i need to do to configure web2py to work > on > > a shared hosting. > > > > I just configured few tables... and modified layout.html to roughly look > > like my PHP site... thats it.. and then tried to measure a single page > > load..... where a PHP page takes around 1 to 2 secs to load fully... > > web2py takes around 6 to 8 secs. On inspecting the sate dump... its WSGI > > section says... Apache supports multiprocess = true but multithreading = > > False and Gateway is CGI 1.1 > > > > Waiting eagerly for some insight or solution... ;) > > > > - regards >
