Comments inline. On Monday, November 25, 2013 11:40:42 PM UTC+5:30, Leonel Câmara wrote: > > Your slow down seems totally expectable. It's spending most of the time > locked or waiting for db. > > You can of course make sure you don't do things that prevent tables from > being lazy but there's not much you can do about the slowdown from > concurrency apart from tuning your database, did you set the pool_size in > your Dal? >
Pool size=100. Number of web2pydaemon processes=10 I didn't get the second point, although I have done caching and database tuning, but it does not matter. I am profiling a http request which make zero database queries and it is being slowed down while loading the models (specifically DAL in db.py). > > What I would do, if possible, would be to aggressively cache as much as > possible so you avoid hitting the DB so much. > > Think about what is really important to be realtime updated, maybe > somethings can be 5 minutes out of date and you can cache that select. > -- 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/groups/opt_out.
