Hi, do you have controller methods that take a relatively long time? For example, at least 0.5 second?
I made a point previously that because session is locked at the beginning of a controller function and is released only at the finish of that function, requests will have to wait one after each other. So unless you explicitly release the lock (via session.forget(response)), there might be a performance penalty. I think so, but I don't know enough to be certain. On Apr 12, 12:52 pm, Ross Peoples <[email protected]> wrote: > I've been developing my application for 6 weeks now and I stay updated with > the trunk version of web2py. I know that Massimo, Johnathan, and others have > been working to increase performance of web2py, but I had to make a Django > app for someone that was similar to one of the web2py applications I built > while teaching myself web2py about a month ago. Running the Django app, I > noticed that the Django app responds around 50 to 100ms faster in some > cases. My app still checks for migrations because I'm still developing it, > so I know that will slow it down a bit. > > Are there some areas where performance can be further improved to squeeze a > little more speed out of web2py applications? Also, is there a good way to > profile applications to find the slowest methods? Web2py is pretty fast > already, but I'm wondering if there are any known areas of slowness (besides > the obvious latency caused by database queries) within web2py that I can > play around with?
