Currently i am coding on an Asus UX32VD Ultrabook (which should have some like an Intel Core i7-3517U 1.9 GHz in it). As of WinVice3.1 using x64 with FastSid does not work correctly anymore. Visuals yes, but Sound sometimes totally goes south (no filters and such).

From the Vice people i was told to use ReSid as FastSid is not supported anymore.

Now my problems start: With using ReSid WinVice drops to like 24fps on my system. Using x64sc with Resid gives me like 8fps.

Looking at procmon it seems like one core is maxed out as CPU load never goes over 24% (the graphs show a different picture as none seems to be properly used).

My workhorse laptop at the office can run x64+resid nicely and properly, but okay it got way more power than my ultrabook will have.

Somehow i got the feeling that my system (Win10 Creators) is not really working properly anymore.

That's why i am asking here.. Any of you guys got a laptop compareable to mine and how's WinVice working on your system? Or what are the general performance reports for WinVice3.1?

Before i go into the ordeal of doing a complete re-install i would like to hear what other experience with WinVice currently. If it's problem on my side, or if it's just how well WinVice works on lower spec (sort of) laptops..

Warp works in 3.1 while the C64 does I/O, albeit slower than 2.4, since 2.4 defaulted to TDE off while 3.1 defaults to TDE on, which means more accurate emulation, sacrificing speed.

If I remember correctly 2.4 also defaulted to non-CRT emulation and FastSID for SID emulation as opposed to 3.x which used CRT emulation and ReSID by default, the biggest bottlenecks in performance, but adding a lot of accuracy.

Then, as Soci mentioned, the codebase was updated removing some speed-hacks but making the code more maintainable. Since there aren't a lot of active VICE devs right now, making sure the code is maintainable with a small team is more important than all sorts of hacks to speed up emulation slightly.

Lastly, disabling cpu-history support and debugging support during compilation will speed up VICE slightly. But the biggest bottleneck I'm aware off is still the SID and CRT emulation coupled with less-than-ideal synchronisation code, which isn't trivial to fix.

So, to get 2.4-like performance: disable CRT, set SID to FastSID, compile without cpu-history/debug (the default for configure), disable True Drive Emulation, enable device traps and hope stuff still works.

you can wait forever for "warp speed optimizations" because that will never happen. what will be optimized is accuracy of the emulation. no idea why you would prefer crappy emulation either =)

the difference you see might be because of the SID emulation settings, which have been changed to be more accurate too. (and I/O being busy is not connected to warp speed at all - except perhaps that more accurate emulation needs more CPU)