| |
Dano
Registered: Jul 2004 Posts: 226 |
WinVice 3.1 speed/performance on Ultrabooks?
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.. |
|
... 51 posts hidden. Click here to view all posts.... |
| |
chatGPZ
Registered: Dec 2001 Posts: 11108 |
a lot with the inability to run at stable 50fps is due to the terrible sound- and sync- code that needs to be deleted and rewritten.
IMHO any i5/i7 should be able to do it fine. my good old amd64 could do it even (ok, with 2.4) :) |
| |
algorithm
Registered: May 2002 Posts: 702 |
Any i3/i5/i7 device with the exception of perhaps a first generation ULV device (e.g i5 520um) should run Vice 3.1 x64sc at full framerate. Even on an Atom Cherrytrail z8700 (GPD Win) it runs fine. 50fps (or near enough)
The I5 3317u (On your device) is enough for vice 3.1 although there has been some severe throttling on some devices
I would probably check the settings in power options. make sure processor max performance is not set to 99% (This will disable turboboost). With adequate cooling, turboboost speeds should hopefully be maintained longer. |
| |
soci
Registered: Sep 2003 Posts: 473 |
As Groepaz said you need to trade off accuracy for performance.
The performance hit is mostly due to default settings changes for 3.0 which were done with the intention of exposing the more accurate emulation features over "half assed" but faster versions.
The point was that it's not possible to optimize for everyone, but at least the defaults should be something "sensible".
Which does not mean it fits exactly your use case or hardware out of the box. It's needs to be tuned.
For coding CRT emulation is counter productive anyway, I switch it off.
Sound I never turn on unless it's needed. Same with true drive emulation, most of the time device traps will do.
When coding mostly calculation heavy effects without tricky timing there's no point running it on X64SC.
If VICE was compiled with memory map or debugging it's going to be slow, so I only use it when really needed for something.
3.x got a little heavier independent of settings, but it's not all that bad yet as it seems. |
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |