I've been working on different things in Decker on my old MacBook pro from 2012 and often find the fans spinning when using the native version. When running it in fullscreen it often takes as much as 50-60% of the cpu and 70% of the gpu. Switching to the js-version in Chrome the same computer is quiet and maxes out at 15% of the cpu . Is there any difference in rendering that makes the native version heavier than the web-version or is it a local phenomenon, ie a problem just on my computer? I'd rather work in the native version as it makes saving so much easier!

(Thanks again for a great tool!)

It shouldn't be dramatically more resource-intensive. There's probably a lot of room for improving performance, especially in Lil's garbage collector.

I can say the native version is much more likely to stick to rendering at the intended 60fps, whereas your browser may be dropping frames (which is mostly unnoticeable, most of the time).

The native version also currently uses SDL's software renderer. If you're on a Mac it's fairly easy to build from source, so perhaps try replacing SDL_RENDERER_SOFTWARE with SDL_RENDERER_ACCELERATED in src/decker.c? Only makes a negligible difference for the devices I've tested, though.

Thanks for your reply!

I have had performance issues on this machine before, so no shadow over Decker. What surprised me is that it handled the web version better than the native build, which intuitively felt backwards, but the (for me unnoticed) drop in fps might be the explanation for that.

I'll definitely try to build Decker with graphics acceleration enabled and see if that makes any difference on my device. I might also experiment with changing the frame rate and see if that makes it calm down.

Thanks again!