RE: Peculiar Win/11 Behavior?

A couple of things to consider:

- Don't discount the possibility of the device or its driver being involved. I think you mentioned MOTU. I'm not sure if it is feasible to substitute another audio device even just for a test run and see if you observe anything different.
- Even with full Sleep (S-states) disabled, modern systems have a complex array of run states for power and thermal management (e.g., D-states, C-states). It would be interesting to know if any dependent device makes a transition in your scenario.

Diagnosing I/O performance in a platform like this can become quite involved (e.g., https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/using-windows-performance-analyzer-to-analyze-modern-standby-issues), but it would be true on any platform. You can certainly try a different platform and get lucky enough to not have to dig 😉.

- Kurt

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of David McClain (as dbm at refined-audiometrics dot com)
Sent: Friday, January 17, 2025 8:48 AM
To: Paul Werkowski <[email protected]>
Cc: Lisp HUG <[email protected]>
Subject: Re: Peculiar Win/11 Behavior?

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.li/
> spworks.com%2Fsupport%2Flisp-hug.html&data=05%7C02%7C%7Cc4ae6411303f47
> f3073e08dd37175271%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638727
> 295519760900%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
> 7C&sdata=6XBFR3W%2BfUhzjKwjDuchdHXme5Eac7Q1p5nfR0pqh6M%3D&reserved=0


_______________________________________________
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