Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user ATOO ! (Registered 2017-11-21) You are not logged in 
CSDb User Forums


Forums > CSDb Discussions > WinVice 3.1 speed/performance on Ultrabooks?
2017-05-12 11:29
dano

Registered: Jul 2004
Posts: 112
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....
 
2017-05-16 16:15
dano

Registered: Jul 2004
Posts: 112
Quote: Quote:
orignal kernel, but got a retro replay or an action replay set as default freezer cartridge.
after pressing F7 the programm loads.

so, basically PEBCAK then :) to make that work reliable, use -keybuf to put a F7 keypress into keyboard buffer after reset (and after a suitable timeout). the autostart mechanism doesnt know about cartridges, nor anything that isnt the original kernal.


Quote:
orignal kernel, but got a retro replay or an action replay set as default freezer cartridge.
after pressing F7 the programm loads.

so, basically PEBCAK then :) to make that work reliable, use -keybuf to put a F7 keypress into keyboard buffer after reset (and after a suitable timeout). the autostart mechanism doesnt know about cartridges, nor anything that isnt the original kernal.


that pretty much NOT explains why it's working at times.

srsly, it happens, then it not happens, .... not happens, happens.. and be sure i tried various things like waiting less, waiting more. yet still if i do it 10 times the same way it can work a random number 0..10.

ofcourse it's easy to blame the user for doing <<RANDOM>> thing wrong instead of finding a solution. guess my collegues can be happy that i am not such a type of coder..

apart from the fact that i don't want to check the compile script or have "compile with f7" and "compile without f7". blabla. welcome to the world of working around quirks because the reason is not to be found or wanted to be found.. ^^
2017-05-16 16:19
Groepaz

Registered: Dec 2001
Posts: 8275
the reason is that autostart uses specific timing constraints. it works sometimes and sometimes not because the timing you press F7 with is not always the same.

and if you dont want to use the solution that actually works... ok. dont blame the emulator for it though, thats just silly =P
2017-05-16 16:48
dano

Registered: Jul 2004
Posts: 112
ah yes, then it makes totally sense why the problem occurs at times with instant f7 pressing or waiting with pressing f7 for a longer time (>10 seconds that is).

and i must admit lame me doesn't know how vice detects when to switch off warp-mode after loading a file.

but honestly this too is offtopic as it was not about "non-existant" vice bugs but rather vice performance (tipps).

thanks again at soci and compyx for comprehensive informations.
2017-05-16 16:57
oziphantom

Registered: Oct 2014
Posts: 161
If you are on Windows, note that VICE can trap all mouse clicks, so if you have something in the clipboard, and right click somewhere you will paste it into the keyboard buffer.. this can wreck havoc on Autostart, or not depending on when you click and what the emulator is doing etc makes it somewhat random.
2017-05-16 22:05
dano

Registered: Jul 2004
Posts: 112
Went through settings and disabled the render filter to none. Switched SID to 8580 Resid. This currently gave me a variable FPS value between 45 to 52 fps. Funny enough emulation speeed variied from 95% to 105% even with emulation speed to 100% normal.

Setting the render filter to "CRT" gave me something like 12fps to 20fps.

On x64 that is.

Does "double size" and "double scan" have much of an effect in VIC emulation?

x64sc is on 68% speed and 15fps..
2017-05-16 23:34
algorithm

Registered: May 2002
Posts: 682
Quote: Went through settings and disabled the render filter to none. Switched SID to 8580 Resid. This currently gave me a variable FPS value between 45 to 52 fps. Funny enough emulation speeed variied from 95% to 105% even with emulation speed to 100% normal.

Setting the render filter to "CRT" gave me something like 12fps to 20fps.

On x64 that is.

Does "double size" and "double scan" have much of an effect in VIC emulation?

x64sc is on 68% speed and 15fps..


Are you sure certainly that your CPU is not throttling? I can even run X64SC (Winvice 3) on a Z8700 based atom laptop with no slowdowns. (And that includes Resid on and double screen/pal emulation)
2017-05-17 08:56
Groepaz

Registered: Dec 2001
Posts: 8275
by far the most CPU is wasted in resid and CRT emulation - all the rest is pretty irrelevant. you shouldnt have that sort of performance problems in any case.
2017-05-17 09:27
dano

Registered: Jul 2004
Posts: 112
@algorithm: got a decent hint for me to check upon throttling and current cpu speeds and such? got such a feeling myself, but up to now my findings didn't bring up a proof for that..

in windows itself the energy settings are re-set to max power.
2017-05-17 10:58
algorithm

Registered: May 2002
Posts: 682
You can try using HW monitor and monitoring temperatures before you run Vice and during. This will show you the multipliers as well as temperatures of the CPU cores.

Usually during boot/reboot, there is more cpu activity. Leave it for a few minutes, run hwmonitor, monitor the multiplier/temperatures, then run vice. Indication of throttling is when the temperatures go up (and multipliers are at a high state) then multipliers reducing after.

For some users, turning off turboboost (set 99% under cpu max speed in power settings) can help (even at non-turbo, your CPU should still have (Just about) sufficient power to run x64sc at 50fps.
2017-05-17 13:17
soci

Registered: Sep 2003
Posts: 375
Quote: Quote:
the terrible sound- and sync- code that needs to be deleted and rewritten.


This is likely only a problem on Win32. According to a quick search the Sleep function used currently is only as good as the timer tick which is rumoured to have a 64 Hz resolution.

First I would say this function in the arch code should be replaced with something better before going for a complete rewrite of the generic part. Maybe just putting a NtSetTimerResolution call somewhere might also do the trick.

I don't seem have sync problems on Linux but that's not a fair comparison as this OS got rid of the fixed 100/1000 Hz ticks many years ago...
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
www.gb64.com
markus sinalco
encore
r242
Alakran_64
Acidchild/Padua
Guests online: 49
Top Demos
1 Uncensored  (9.7)
2 Edge of Disgrace  (9.7)
3 Coma Light 13  (9.6)
4 The Shores of Reflec..  (9.6)
5 Lunatico  (9.6)
6 Comaland 100%  (9.5)
7 Incoherent Nightmare  (9.5)
8 Wonderland XII  (9.5)
9 Comaland  (9.5)
10 Wonderland XIII  (9.5)
Top onefile Demos
1 Pandemoniac Part 2 o..  (9.6)
2 FMX Music Demo  (9.6)
3 Daah, Those Acid Pil..  (9.5)
4 Dawnfall V1.1  (9.5)
5 Synthesis  (9.5)
6 Dawnfall  (9.4)
7 Treu Love [reu]  (9.4)
8 Field Sort  (9.4)
9 Pro Memoria 4  (9.3)
10 KAOS 64  (9.3)
Top Groups
1 Oxyron  (9.4)
2 Booze Design  (9.4)
3 Censor Design  (9.3)
4 Crest  (9.3)
5 The Judges  (9.3)
Top Organizers
1 Burglar  (9.9)
2 Wotnau  (9.7)
3 Sixx  (9.7)
4 MWS  (9.7)
5 Frantic  (9.6)

Home - Disclaimer
Copyright © No Name 2001-2017
Page generated in: 0.985 sec.