CPU utilisation
Hi Manolis,
I'm sorry to hear this bad news.
Just for comparison, here are some figures on my pc under W10:
wdm.exe: 1%
DiAna-1: 5%
DiAna-2: 10%
Motherboard: MSI-B75A-G43, CPU: Intel i5-3570K 3.40GHz
But sometimes TiWorker.exe starts spontaneously to run, consuming about 25% of CPU resources. Under these circumstances, I also get DAC underrun errors.
Also, after startup, I have to wait for at least 15 minutes before W10 calms down. It's really a horrible OS. For the time being, I stick with W7.
Cheers, E.
Hi Manolis,
I'm sorry to hear this bad news.
Just for comparison, here are some figures on my pc under W10:
wdm.exe: 1%
DiAna-1: 5%
DiAna-2: 10%
Motherboard: MSI-B75A-G43, CPU: Intel i5-3570K 3.40GHz
But sometimes TiWorker.exe starts spontaneously to run, consuming about 25% of CPU resources. Under these circumstances, I also get DAC underrun errors.
Also, after startup, I have to wait for at least 15 minutes before W10 calms down. It's really a horrible OS. For the time being, I stick with W7.
Cheers, E.
On my systems Win 10 seems pretty stable and I have not seen any issues with startup after its fully booted. In some cases background virus checks and drive indexing will be an issue. I saw not underruns or other errors on the test system (amd 4 core processor). I'll try it on some other systems just to confirm.
Which is more demanding of the system, lots of lower depth samples (1K) or fewer high depth samples (128K)?
Which is more demanding of the system, lots of lower depth samples (1K) or fewer high depth samples (128K)?
Windows 10 performs better than Windows 7 for most things. I suspect there are other issues at hand. Especially with systems that have dropouts. There is a misbehaving driver using too much kernel time probably. ISRs and deferred procedure calls taking too long are not Microsoft problems generally, but with 3rd party drivers. Windows is not an RTOS and the NT kernel scheduler does not have bounded latency.
For those who dislike the Windows store stuff, I'd recommend you download Windows 10 LTSB and activate it with a KMS activator if you are comfortable doing that. I'd recommend you just buy it, but you can't buy it without a volume license agreement.
I've installed Windows 3.0 via 5.25 floppies, so I'm probably old enough
. Cut me a break though, I need an emoji or something to detect sarcasm .
Hi Chris,
BTW, as for using plain old C, do you think modern programming techniques make DiAna faster? I think it's rather the opposite (and creating even more dropouts).
Cheers, E.
I did just that.
BTW, as for using plain old C, do you think modern programming techniques make DiAna faster? I think it's rather the opposite (and creating even more dropouts).
Cheers, E.
I've installed Windows 3.0 via 5.25 floppies, so I'm probably old enough
Okay I Admit it was a bit dry.
I've installed RT-11 via 8" floppies, so I'm probably too old.I've installed Windows 3.0 via 5.25 floppies, so I'm probably old enough
(note: "RT" stands for real-time !!!)
Hi Chris,
I did just that.
BTW, as for using plain old C, do you think modern programming techniques make DiAna faster? I think it's rather the opposite (and creating even more dropouts).
Cheers, E.
Generally you are right, but GDI drawing performance may be lower on Windows 7 and later compared to Direct2D/Direct3D. It depends on what's driving your CPU utilization.
Overall, no one should get dropouts even with relatively high CPU utilization, it's almost a different problem. I can run Prime95 Torture Test on all CPU cores and not drop any audio samples.
The worst OS ever
@ Chris,
GDI drawing during data acquisition doesn't burn that much CPU cycles. Under W7 only 1.5% and under W10 2.3%, at least on my PC. Instead, the massive calculations consume most of CPU resources (3 times more than GDI stuff). So, I'm afraid, using Direct2D/Direct3D will not speed up that much and cure the issues with W10. It's that f*****g Windows Modules Installer Worker for example (and other useless background tasks) that consumes up to 50% of the CPU power. No wonder one will get dropouts.
W10 is an OS for stupid cell phones and definitely unsuitable for time critical applications on a PC. In this respect, W7 does a better job.
Cheers, E.
@ Chris,
GDI drawing during data acquisition doesn't burn that much CPU cycles. Under W7 only 1.5% and under W10 2.3%, at least on my PC. Instead, the massive calculations consume most of CPU resources (3 times more than GDI stuff). So, I'm afraid, using Direct2D/Direct3D will not speed up that much and cure the issues with W10. It's that f*****g Windows Modules Installer Worker for example (and other useless background tasks) that consumes up to 50% of the CPU power. No wonder one will get dropouts.
W10 is an OS for stupid cell phones and definitely unsuitable for time critical applications on a PC. In this respect, W7 does a better job.
Cheers, E.
Torture Test
Hi Chris,
I've also run the Prime95 Torture Test together with DiAna and a 99% CPU utilization. No problem at all, under W7 as well as W10. But before I could use W10, I had to wait another 30 minutes, as W10 was again busy with system rubbish. Apparently it is this rubbish that has a higher priority and hence is responsible for dropouts.
Today, I started W10 three times and in every case I had to wait 30 min. before W10 was really ready. That makes 1.5 hours. So W10 is not only a real-time OS, it is even stealing my time!
Cheers, E.
Hi Chris,
I've also run the Prime95 Torture Test together with DiAna and a 99% CPU utilization. No problem at all, under W7 as well as W10. But before I could use W10, I had to wait another 30 minutes, as W10 was again busy with system rubbish. Apparently it is this rubbish that has a higher priority and hence is responsible for dropouts.
Today, I started W10 three times and in every case I had to wait 30 min. before W10 was really ready. That makes 1.5 hours. So W10 is not only a real-time OS, it is even stealing my time!
Cheers, E.
So Bill Gates should pay me for using W10.
Yup. And me too.
We should start a class action suit.
I've installed RT-11 via 8" floppies, so I'm probably too old.
(note: "RT" stands for real-time !!!)
same here... RT-11. Commodore PC. pre IBM PC.
man, I am old now.
-RM
Hi Chris,
I've also run the Prime95 Torture Test together with DiAna and a 99% CPU utilization. No problem at all, under W7 as well as W10. But before I could use W10, I had to wait another 30 minutes, as W10 was again busy with system rubbish. Apparently it is this rubbish that has a higher priority and hence is responsible for dropouts.
Today, I started W10 three times and in every case I had to wait 30 min. before W10 was really ready. That makes 1.5 hours. So W10 is not only a real-time OS, it is even stealing my time!
Cheers, E.
I tend not to upgrade OS in case my PC applications are stable and working well. I also write now from ASUS, under Win8.1. I have ignored all the Microsoft appeals to upgrade to Win10, because the PC and apps work well with Win8.1. I will rather buy a new machine later, than to upgrade to new OS. Do not have good experience with OS upgrade. Updates of the existing OS are a different case.