> - Both my develop machine (windows xp home edition with latest ServicePack), > and my production machine (a Linux), have such issue occasionally. Both > environments uses web2py's built-in server, rocket or cherrypy. Both serve no > more than 10 people or so.
> @Massimo: You can check your production server's httpserver.log to see what > is the longest (slowest) response time. If it is small enough, that is good, > otherwise ... oh by the way, do you use web2py's built-in server (now > rocket), or do you use apache-like frontend? That could make difference. I moved to apache/WSGI from Rocket. For me the problem disappears.