-
Notifications
You must be signed in to change notification settings - Fork 2
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
CPU cycling fixes #165
CPU cycling fixes #165
Conversation
Don't forget to connect this to the corresponding issue. |
329133a
to
4e68f61
Compare
I rebased this with the main branch so it can be merged. You will need to delete your local branch then pull down this remote branch if you want it on your computer. Otherwise, you may have some issues trying to pull it down into your existing local branch. Anyway, I pulled down this branch and ran the imagemagick_files.py example. The example ran fine and my CPU usage remained below 1%. Good job! |
Closes #161 |
@wigging sounds good! I linked the issue and made sure it's passing the ruff checks. Confirmed tests and imagemagick still run on rebased version. |
I think you committed a bunch of files that should be ignored. |
fe165da
to
c3907e0
Compare
c3907e0
to
47c9b40
Compare
I reverted the last commit which added a bunch of unrelated files and force pushed the change. I think we're good to go now. |
In this branch I changed how we accessed internal queues to 'ease up' on the CPU.
Please test using the following:
zambeze start