Subj : CPU Hog
To   : Digital Man
From : deon
Date : Sat Aug 06 2022 12:34:17

  Re: CPU Hog
  By: Digital Man to deon on Fri Aug 05 2022 01:07 pm

 >  > Is there a way to "busy out" the polled node, so another thread doesnt try and call it again?
 >
 > The SBBS event thread is a single thread. BinkIt polling is normally done as a timed event, which is run as in the foreground of
 > that single event thread. So I'm not clear what "another thread" would be.

OK, so I have BINKPOLL (binkit -p) set to run 2 times per day.

So are you suggesting that when SBBS runs it, it can never run a subsequent time, if the previous run never completes?

My logs show it does run twice a day (not 12 hrs apart, ergo 2 times a day - but...)

Aug  5 00:35:54 d-11-1 synchronet: evnt BINKPOLL Running native timed event: BINKPOLL
Aug  5 14:36:58 d-11-1 synchronet: evnt BINKPOLL Running native timed event: BINKPOLL

So if the first question is yes, then that would imply that binkit -p does eventually exit.

I'm wondering then, what else could cause the CPU goes to 100% on 2 threads for an extend period of time? (I havent monoitored the time, but my vmware logs show it was pegged for 2 hrs before I intervened.)

Since my fido link identified the cause (it seemed it was in his end), CPU is backed to < 5%.


....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!

.