Re: Peculiar Win/11 Behavior?

Well before sustemd it was very easy - you simply verify your crontabs and know when is something schedulled.
Nowadays you need to look at systemd timers, but for server there is a very limited number of systems/processes running. But the basic is that it is rather on one place (or today maybe 2 places) where you can check planned executions. Also paging can be fine-tuned in kernel while system is running (so you can force kernel to swap only in exceptional cases) 

For windows this is inclear what is running and why. If i open windows services, i do not have a clue on at least half of them. All those keep on running and you need to check schedulers and hope there will be no push of policy if you are inside a company. 

So in essence it is less predictable with more potential disruption for data collection service. Maybe some well tuned server version of windows is better at this but consumer grade windows expect only human at interface so occasional hiccups are no issue ;) also windows and mac tend to have data collection about system usage reporting back to companies. Linux does not seem to have such a thing.

On linux you can turn off allmost all services and system will be running just fine with minimal if any disruption. You still have option to log in once a quarter and request updates and patches to be installed.
Just my 2 cents.


Ladislav Koščo 


> On 17 Jan 2025, at 11:24, David McClain <[email protected]> wrote:
> 
> Well, Linux, Mac OS, and WIndows, all have things running in the background. What is it about Linux that allows you to prevent interference? How do you do that?
> 
> 
> 
> 
>> On Jan 17, 2025, at 03:12, [email protected] wrote:
>> 
>> Windows tend to do background patch downloads as well as some security tools like antivirus or antimalware scanners might get involved.
>> For such workload you are describing i will most probably use linux machine so i can prevent such behavior.
>> 
>> Not to mention that on company laptop sometimes there is some processing that will freeze whole experience for almost 30 seconds….
>> 
>> 
>> Ladislav Koščo
>> 
>> 
>>>> On 17 Jan 2025, at 11:02, David McClain (as dbm at refined-audiometrics dot com) <[email protected]> wrote:
>>> 
>>> I am doing a long running data collection process, all written in Lisp, on a Win/11 system.
>>> 
>>> I notice that there are periods in the evening when my acquisitions suffer some phase discontinuities, which cause the data to exhibit higher than normal statistical variances. And often, on the longest duration collections, the system loses phase coherence completely, requiring that I shutdown the Lisp app and restart it to clear things up. There seems to develop a permanent disjunction between the Lisp data requests and the underlying Windows I/O system. That has to be my fault, but after instrumenting the system, I have yet to find hard evidence of where that happens and when.
>>> 
>>> My timings between data buffer requests should all be less than 500 ms. They normally range between 4-20 ms. Last night I see in the historical record there was one instance of a delay of 486 ms - almost long enough to lose phase coherency, which seems to have happened around 11 pm local time. It is now almost 3 am local time.
>>> 
>>> The Lisp code is completely asynchronous, but there is nothing that should be causing isolated instances of delays 20x longer than the nominal max of 20 ms.
>>> 
>>> I’m running the system with Sleep deferred while data collection activities are under way. So ports going to sleep should not be a problem. The screen remains lit up the entire time and no screen saver gets instantiated.
>>> 
>>> So, I’m wondering if anyone else sees erratic behavior in the evenings with Windows/11? Could there be some daemon scheduled to run at night that causes I/O activity to go bonkers from a regular precise schedule? Is Windows so totally bolluxed that it is insane to be attempting scientific data collection with it?
>>> 
>>> (We used to have dedicated VME crates with our own processors and realtime OS to do this kind of work.)
>>> 
>>> 
>>> _______________________________________________
>>> 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