I also noted best performance directly rendering the templates and caching views where it can be cached.
just replacing return dict() with return response.render(filename, context) in conttrollers and also usins @cached controllers and cached queries. the bottleneck is always server and database, so it is better to use pure Python to sort, find, filter Rows objects than using a lot of database requests. DAL provides .sort .find .exclude and Python has a lot of good things like map, reduce, filter. With one db request you can fetch records put them in cache and use Python in some cases to avoid more sql queries. Even paginations can be done without the need to go to db again. Redis is being a good cache solution. http://zerp.ly/rochacbruno Em 27/01/2012 13:40, "Alfonso de la Guarda" <[email protected]> escreveu: > Hi, > > I'm about to start a major project development and although I am a > regular user of web2py in my development, they have been mostly in > intranets, what worries me is if anyone has had previous experience of > putting an application based on web2py with several thousand users, in > which case I would like your job with this. > > Previously, I have dealt with a project based on django super (500000 > unique users month) and problems of performance, scalability and > others were so serious that they chose to pass it to php, I would not > do the same with this application in web2py. > > > Thanks.... > > Saludos, > > -------------------------------- > Alfonso de la Guarda > Centro Open Source(COS) > http://www.cos-la.net > http://alfonsodg.net > Twitter: @alfonsodg > Redes sociales: alfonsodg > Telef. 991935157 > 1024D/B23B24A4 > 5469 ED92 75A3 BBDB FD6B 58A5 54A1 851D B23B 24A4 >
