Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry CPU al 100% #103

Closed
cent89 opened this issue May 20, 2020 · 2 comments · Fixed by #132
Closed

Raspberry CPU al 100% #103

cent89 opened this issue May 20, 2020 · 2 comments · Fixed by #132
Labels

Comments

@cent89
Copy link

cent89 commented May 20, 2020

Hi, thanks for your project!
I've installed FQM on Raspberry PI 3+, running in cli mode with:

python3 run.py --cli --ip 192.168.7.100 --port 3790 --quiet

It works well but I have two problems:

  1. While a display screen is opened, the whole system is too slow; python use the 90-100% of CPU! It's normal? There are some min requirements?

  2. I've installed a POS printer, and the test page from CUPS is ok. But in FQM, after a button service is pressed, the page loops forever, even if the python process uses 2-3% of CPU. Where is the problem?

Thanks!
Roberto

@mrf345
Copy link
Owner

mrf345 commented Jun 4, 2020

Unfortunately i won't have enough time to reproduce it locally. if someone else wants to give it a try https://azeria-labs.com/emulate-raspberry-pi-with-qemu/

@mrf345
Copy link
Owner

mrf345 commented Jun 9, 2020

I took another look today and was able to reproduce it. Turns out a front-end interval was emitting too many requests to the back-end.

I'm about to merge some refactoring #132 to reduce them. And now you should be able to control that behavior through Customization > Display Screen > Preferences > Refresh Rate The default is set to 2 seconds, you can always increase it for better performance but expect the display screen to get slower:

display_refreash_rate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants