Recently, I've been seeing one of my test web2py servers get bogged down, and sometimes fail to respond to the user. When this happens, I find the web2py.log file is getting filled with lines like
2022-03-29 17:38:31,480 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:38:46,710 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:38:47,776 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:39:00,003 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:39:21,467 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:40:21,421 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:41:21,367 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) 2022-03-29 17:42:21,348 - web2py.scheduler.Dave-PC#8844 - DEBUG - defining tables (migrate=True) This continues even if the user (me) stops making requests. This being Windows, I launch the server using the little GUI tool that includes a traffic monitor (seismograph of incoming requests), and that shows a regular tick that isn't connected with my clicking any links. The server version info: web2py™ Version 2.21.1-stable+timestamp.2020.11.28.04.10.44 Python Python 2.7.16 (bundled) The front end is the bundled Rocket code. The client is Chrome: Version 99.0.4844.82 (Official Build) (64-bit) Both client and server are on a laptop: Edition Windows 10 Pro Version 21H1 Installed on 11/15/2020 OS build 19043.1586 Experience Windows Feature Experience Pack 120.2212.4170.0 I do have a model for a scheduler task, but I usually don't fire up the scheduler process. If I change the filename for that model to scheduler.py.hidden, I don't get those scheduler log entries, but the seismograph still shows an event about once a minute. httpserver.log says it's the same three requests each time: 92.168.4.21, 2022-03-30 02:42:21, GET, /admin/todolist.load, HTTP/1.1, 303, 0.043000 192.168.4.21, 2022-03-30 02:42:21, GET, /admin/index.load, HTTP/1.1, 404, 0.081000 192.168.4.21, 2022-03-30 02:42:21, GET, /badlist/appadmin/hooks, HTTP/1.1, 200, 0.284000 With older versions of web2py and Chrome, I've seen what I call "cache thrash"; where Chrome seemed to be issuing a blizzard of requests to refresh the cache, and web2py couldn't respond to anything else. This would continue until I stopped the server, which often required a process kill. Am I see a less vicious form of cache thrash? I became aware of this current version of the problem when using a "public" port that is visible on the local network (having bought a new laptop), but I don't think that's the source of the problem, and the earlier version of the problem was only using 127.0.0.1 (localhost). /dps -- 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 web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/544ac26e-672f-40a2-b204-c5921e6eaa35n%40googlegroups.com.
