Hi;
On the latest DietPI edition i’ve noticed that every Amiberry version I’ve run CPU usage is always limited to 25-30%, and with higher load from application - CPU is still blocked at this level. This of course causes Amiberry to slow down. I checked on Amiberry versions from 5 to 7 and with Lite versions too - always the same magical behavior, CPU is blocked.
I did a stress test for the CPU and it ran at full utilization.
CPU usage checked at different levels, also Performance. Still the same behavior with this app.
What could be causing this Amiberry/CPU behavior?
This is probably normal for the vast part of the core emulator. Have you tested it on RPi OS?
Yes, one of the tested versions of Amiberry came from PiMIGA and there it worked dynamically on the CPU. Something here doesn’t seem right to me…
As far as I know, PiMIGA is a special operating system for Amiberry. So the comparison is somewhat difficult. Perhaps the developer of PiMIGA has made adjustments that allow parallel execution.
Hence the question of how the whole thing behaves on a regular RPI OS.
Yeah so what would be important to know is the kernel version and build PiMIGA is using. DietPi is shipping with the RPi OS repo and hence shares the same kernel and firmware.
Then PiMIGA uses the same Amiberry version? I.e. v7 there?
I am currently working on Amiberry v7 for DietPi. One difference compared to v5 is that device specific flags like DispmanX API usage for RPi are gone. While we removed it a bit earlier already, as the API is deprecated and related library not shipped anymore with recent RPi firmware packages, it was still possible to compile Amiberry v5 against it (instead of true DRM/KMS), if lib headers were present etc. DispmanX allowed multi-threaded drawing, so it might have something to do with it.
Amiberry v7 and Amiberry-Lite do not support it anymore. So if PiMIGA runs Amiberry better despite these, the reason must be a different one. I cannot imagine that the kernel can be the reason, but who knows.
Other than that, as we ship our Amiberry builds with embedded newer and optimised SDL2, I suggest testing our builds once done, also along with the systemd unit which starts it via DRM/KMS directly, not X11 or similar. Not sure how you compile or start it, might make a difference.
DietPi with desktop LXDE, run as windowed linux app.
Not sure if we misunderstood but question was a different one
That may be however a dedicated reason for bad performance. You run it the same way on PiMIGA? Does PiMIGA use X11 or Wayland? And did you enable DRM/KMS on your DietPi system?
Running it via DRM/KMS instead of via window manager should work much better.
As I remember, PiMIGA 3 based on RPiOS and X11, but have to check. For sure, as in this case, I could run AmigaOS builds in windows, in the XFCE environment. And it was a standalone Amiberry compilation.
I’ve tried today Amiberry 7.0.8 and Amiberry-Lite 5.8.8 and the last one works far better on my RPi 4b DietPi LXDE aarch64.