Does WinUAE performance degrade with lots of use?

[Foebane]

I am not sure if this is WinUAE or just Windows 10, but I encountered an unusual situation the other day that I've noticed before, but this time to a large extent:

I had spent an evening running several demos, one after the other, usually warm rebooting each time, and thisthis particular demo didn't run all the way through, without corruption or blank screens or just plain freezing. I figured I'd just restart Windows and resume, but it actually got worse, with audio glitches and so forth. The whole time, I was running the above files from the same folder I keep all my Amiga demos in, and I figured that the SSD drive I was using was failing (though I know it shouldn't, if it's just reading the data). So I then proceeded to delete the Amiga folder and re-extract all the files into the same Amiga folder as before, and the issue persisted.

The next day, I thought I'd try extracting just the disk images for this demo into a temporary folder, away from the Amiga folder... and it played through fine. So the usual files from the Amiga folder didn't work but these temporary files did. So I did a file comparison through Windows CMD (FC) and the files were identical. Later on that morning, I thought I'd run the usual files as I did before (and didn't work) - but this time they DID.

Basically, it seems to boil down to the performance of WinUAE, as if some cache or RAM hasn't been cleared even when Windows restarts, or if it's something else. It's not only happened with this demo, but other freezes occur quite rarely, and I just do a cold reset and carry on, or just restart Windows.

Any idea what could be causing this phenomenon? It's not my SSD, as SSDlife says it's healthy.

[AMIGASYSTEM]

If the problem is only on the SSD, try to do a scandisk on the SSD.
If the problem is in any path, try on WinUAE to click on "Clear Disk History","Reset To default " from the" Menu Path"

[Toni Wilen]

Because no useful info included: Standard answer: fastest possible CPU/UAE directory/hardfile timing is variable depending on lots of things. You can NEVER duplicate exact same timing again.

[Foebane]

Originally Posted by Toni Wilen

Because no useful info included: Standard answer: fastest possible CPU/UAE directory/hardfile timing is variable depending on lots of things. You can NEVER duplicate exact same timing again.

To be honest, aside from the demo link itself, I'm not sure what information to provide that would be the source of the problem. Sorry. But as you've explained, it's down to lots of things. I just thought it was a strange phenomenon that attention ought to be drawn to, that's all.

[AC/DC HACKER!]

Without logs Toni isn't able to help well. I would type that Windows 10 isn't very good and I stay with Windows 7, but that's not helpful to Toni either. Describing a strange "phenomenon" and pointing to your personal experience won't aid in becoming fixed alone.

Do it all again, as Toni suggested, without the CPU emulation speed "Fast as possible" enabled. Create logs after that change. That's the information to provide.

[Foebane]

Originally Posted by AC/DC HACKER!

Do it all again, as Toni suggested, without the CPU emulation speed "Fast as possible" enabled. Create logs after that change. That's the information to provide.

What? What makes you think I used "fastest possible" in the first place? I don't use that at all now, except for tasks like extracting a lot of LHA archives, and I did NOT use it last time. Why do people assume I still use it for regular emulation???

[Toni Wilen]

I recommend Windows 10. Never assume anything (Seriously, as long as Windows 7 or newer and major hardware is still supported, as in drivers are not from 2 years ago: it is fine. If not, I am not that interested in doing any non-trivial debugging)

If you don't use fastest possible: copy all files from UAE hardfile/directory to RAM disk first. This guarantees repeatable access times.