even in a single process you shouldn't notice any "unresponsiveness". it's most likely that locally you have both the browser process and webp2y competing for resources than a problem on the thread executing the work (as the default webserver is multi-threaded). Another thing to consider with ajax is that by default web2py serializes session access, so you may be experiencing a delay from when you queue the task to when it gets really executed, but it still won't be noticeable in the web page requesting it (still, consider using session.forget(response) at the top of your controller receiving the ajax req if you don't need session).
On Saturday, June 4, 2016 at 2:02:18 AM UTC+2, Mark Smith wrote: > > I just tried switching to a simple ajax call and like you said and it's > much faster (and there's no unresponsiveness :) ) on pythonanywhere. When I > test it locally I see a bit of unresponsiveness but I think that's because > pythonanywhere has webworkers while locally there's only a single > non-threaded web2py process? > > Thanks for all the help Niphlod! Really appreciate it :). > > >>>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
