> What could it be? let's rule things out > - cron when it runs spikes CPU usage. DO NOT USE. In production run not the case. no cron, no cpu spikes
> - web2py session lock (the the same user can only access one page at I have session.forget.. > - sqlite lock (depending on the query and the complexity of not the case, I use mysql now > - db connection pooling locks (when look up for open connection) how to check this? I even did pool_size=10 but I never have more than 3 users at once I think it does not help > - cache locks (it is a global lock, to ensure data integrity) how to debug this? > - cache.ram can cause memory leaks if the key depends on variables no memory leaks noticed > - problem with web server (Rocket or the apache or mod_wsgi, etc.) I use Rocket now, I don't know when I will be able to migrate to wsgi, probably soon
