I am using the Raspberry Pi for a "Bowshooting Cinema" (bogenschiesskinos.de).
The Software is basically written in Python including some libraries.
It is (was) working on RPI3 and RPI4 under Raspbian starting with "Jessie", continuing with "Stretch" and up to "Buster" fluently and without any problems.
Now I changed the "trigger" mechanism from a loud impact noise (via Microphone) to a signal from a movement detector (basically a spiral around a fixed rod).
I thought I experienced some problems with interrupts on the GPIO ports and I might solve them by using the most current Operating System.
Therefore I tried the Software with the latest version of "Bookworm" (downloaded, installed and upgraded in January 2024).
There are LOTS of issues with "Bookworm", I do not want to discuss here.
It works pretty well with the old RPI3 models. The interrupt handling has improved and I am not missing the interrupts, I have missed under "Buster". BUT with my RPI4 models the software is creeping as slow as a snail. Even the mouse pointer does not move. If an Impact is recognized, it even takes a noticable time, until it is processed. The animation is anything but smooth. The overall performance is completely disappointing compared to an RPI3, which is behaving like charme, even under "Bookworm".
What I have observed so far is, that "Wayland" (the X-Server replacement") takes 50% of the (one) CPU time.
I suspect, that in this special case (RPI 4 + "Bookworm") the working process is not given to another CPU. It seems to just run on one CPU.
(My "bowshooting Cinema" uses "Multiprocessing" in several ways, which might result in a poor performance if it is all performed on one CPU)
I have read about some performance issues with RPI4 and Bookworm in this forum before, but it did not seem to have resulted in an appropriate solution. There must be something going wrong completely with RPI4 (and not with RPI3)!
Best Regards
Rainer Kowallik
The Software is basically written in Python including some libraries.
It is (was) working on RPI3 and RPI4 under Raspbian starting with "Jessie", continuing with "Stretch" and up to "Buster" fluently and without any problems.
Now I changed the "trigger" mechanism from a loud impact noise (via Microphone) to a signal from a movement detector (basically a spiral around a fixed rod).
I thought I experienced some problems with interrupts on the GPIO ports and I might solve them by using the most current Operating System.
Therefore I tried the Software with the latest version of "Bookworm" (downloaded, installed and upgraded in January 2024).
There are LOTS of issues with "Bookworm", I do not want to discuss here.
It works pretty well with the old RPI3 models. The interrupt handling has improved and I am not missing the interrupts, I have missed under "Buster". BUT with my RPI4 models the software is creeping as slow as a snail. Even the mouse pointer does not move. If an Impact is recognized, it even takes a noticable time, until it is processed. The animation is anything but smooth. The overall performance is completely disappointing compared to an RPI3, which is behaving like charme, even under "Bookworm".
What I have observed so far is, that "Wayland" (the X-Server replacement") takes 50% of the (one) CPU time.
I suspect, that in this special case (RPI 4 + "Bookworm") the working process is not given to another CPU. It seems to just run on one CPU.
(My "bowshooting Cinema" uses "Multiprocessing" in several ways, which might result in a poor performance if it is all performed on one CPU)
I have read about some performance issues with RPI4 and Bookworm in this forum before, but it did not seem to have resulted in an appropriate solution. There must be something going wrong completely with RPI4 (and not with RPI3)!
Best Regards
Rainer Kowallik
Statistics: Posted by Rako62 — Sun Feb 04, 2024 8:22 pm