Conversation

Notices

1. Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 01:17:03 UTC Bernie

   VICE 3.7 is out with lots of improvements!

   https://vice-emu.sourceforge.io/
   #vice #c64 #vic20 #c128 #retrocomputing #emulators

   • Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 01:54:08 UTC Bernie

     in reply to

     • @living8bit

     @living8bit You could try compiling it with --enable-sdl2ui to see if it makes a difference.

   • @living8bit (living8bit@mastodon.social)'s status on Tuesday, 27-Dec-2022 01:54:09 UTC @living8bit

     in reply to

     @codewiz

     Compiling now. I fear the CPU usage is still going to be huge as compared to 3.3. They blamed GTK for it, but I have 3.3 with the newer GTK libs from Deb11 and the CPU usage *isn't* higher.

     We shall see...

   • Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 02:02:16 UTC Bernie

     in reply to

     • @living8bit

     @living8bit I just launched x64sc, and I see 51-53% CPU usage on a single core of a i7-12700F.

     This measurement is taken at the "READY." prompt, PAL mode, no UI scaling, bicubic render filter, v-sync enabled, CRT emulation enabled, etc.

   • Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 03:18:29 UTC Bernie

     in reply to

     • @living8bit

     @living8bit Here's what I got with a quick pprof run.

     81% of the CPU goes into vicii_cycle(), and 51% in vicii_raster_draw_handler().

     This is an optimized build and I have no time to dig more into it, but nothing is pointing at GTK...

     #programming #profiling #linux

   • @living8bit (living8bit@mastodon.social)'s status on Tuesday, 27-Dec-2022 03:18:30 UTC @living8bit

     in reply to

     @codewiz

     Ok, I'm going to need to do some more experimentation. Below is v3.3 x64 at 6.6% CPU, v3.7 x64sc at 56% CPU, and v3.7 x64 at 6% CPU. I didn't check my settings, but there may be hope!

     (Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz, 8cores)

   • Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 06:51:31 UTC Bernie

     in reply to

     • @living8bit

     @living8bit no problem, I'm also curious!

   • @living8bit (living8bit@mastodon.social)'s status on Tuesday, 27-Dec-2022 06:51:33 UTC @living8bit

     in reply to

     @codewiz

     I done messed up. My fingers 'cd'd into my 3.3 directory out of muscle memory. I just ran x64sc and x64 for v3.7 and the CPU is off the charts. It does go to show though how 3.3 is just much less stressful on the CPU.

     As for pprof, I don't have the means to run it, but if you got 51% on an optimized build, I still don't see it matching v3.3 levels on my machine. Whatever the actual cause, that's too much CPU usage for me to switch at this point.

     (For ref: https://sourceforge.net/p/vice-emu/bugs/1017/)

   • @living8bit (living8bit@mastodon.social)'s status on Tuesday, 27-Dec-2022 06:51:33 UTC @living8bit

     in reply to

     @codewiz

     Hmmm. Check the CPU usage under XFCE's Task Manager, and it's giving me 14-18% depending on PAL or NTSC, but my CPU graph taskbar widget shows much more 14% activity when the emulators running.

     I'll play more later too. Have a good night and sorry for the bombardment of toots on the matter.

   • @living8bit (living8bit@mastodon.social)'s status on Tuesday, 27-Dec-2022 06:51:34 UTC @living8bit

     in reply to

     @codewiz

     Even more peculiar then based on the mailing list response I saw years ago. Thanks for the hint to pprof though...

   • Bernie (codewiz@mstdn.io)'s status on Tuesday, 27-Dec-2022 07:52:17 UTC Bernie

     in reply to

     • @living8bit

     @living8bit I guess it's hard to measure the effective CPU usage these days, because the clock frequency also changes depending on usage and thermal conditions.

     There should be a /sys file to force the cores to run at the maximum frequency, which is good for benchmarks.