Re: Peculiar Win/11 Behavior?

"David McClain (as dbm at refined-audiometrics dot com)" <[email protected]>
Newsgroups gmane.lisp.lispworks.general
Message-ID <[email protected]>
Yes, I just looked at doing that. Windows Task Manager allows me to elevate the priority of processes. It is unclear whether spawned threads inherit the priority of the parent process or not.

I did notice that all of my Actor message dispatch threads have priority 0, both Mac and Windows. And on Windows all the LW Tools (Editor, REPL, etc) have priority 60000000 (Hex? Decimal?). At any rate, I can try to invent these threads with elevated priority.

I can’t really state that the problems only happen in the evening. I was running the other day, and it seems that after about 6-8 hours of data collection, the Windows I/O system gets badly out of sync. Even restarting the app from within Lisp, which closes and then re-opens the I/O, didn’t help. I had to exit the Lisp process entirely, and restart. I am dependent on the MMIO system in Windows for the main data collection. I am mostly a passive client of whatever Windows can achieve.

It would be nice to try Linux for this purpose, but I don’t have any A/D drivers for my MOTU interface under Linux. And MacOS is out of the question for now, since I don’t know how to read the A/D channels directly, even though the driver issue is not a problem. Maybe easier than I think under MacOS?

- DM

> On Jan 17, 2025, at 09:15, Paul Werkowski (as pw at snoopy dot qozzy dot com) <[email protected]> wrote:
> 
> Run the real time threads with elevated priority?
> 
> 
> 
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> [email protected]
> http://www.lispworks.com/support/lisp-hug.html


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.