Well, I was thinking of following the socketserver / handle layout of code and execution, for now anyway.
It wouldn't be a big deal to make them block, but another option is to increase the sleep period 100% for every 200 waiting connections while waiting in handle. Another thing is that it's nice to see Python handling 500+ threads without problems. :) -Morten On Thu, Jul 28, 2022 at 11:45 AM Chris Angelico <ros...@gmail.com> wrote: > On Thu, 28 Jul 2022 at 19:41, Morten W. Petersen <morp...@gmail.com> > wrote: > > > > Hi Martin. > > > > I was thinking of doing something with the handle function, but just this > > little tweak: > > > > > https://github.com/morphex/stp/commit/9910ca8c80e9d150222b680a4967e53f0457b465 > > > > made a huge difference in CPU usage. Hundreds of waiting sockets are now > > using 20-30% of CPU instead of 10x that. > > .... wait, what? > > Why do waiting sockets consume *any* measurable amount of CPU? Why > don't the threads simply block until it's time to do something? > > ChrisA > -- > https://mail.python.org/mailman/listinfo/python-list > -- I am https://leavingnorway.info Videos at https://www.youtube.com/user/TheBlogologue Twittering at http://twitter.com/blogologue Blogging at http://blogologue.com Playing music at https://soundcloud.com/morten-w-petersen Also playing music and podcasting here: http://www.mixcloud.com/morten-w-petersen/ On Google+ here https://plus.google.com/107781930037068750156 On Instagram at https://instagram.com/morphexx/ -- https://mail.python.org/mailman/listinfo/python-list
