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

CherryPy support with Python 3 #3971

Open
1 task done
Alterrien opened this issue Jan 24, 2025 · 0 comments
Open
1 task done

CherryPy support with Python 3 #3971

Alterrien opened this issue Jan 24, 2025 · 0 comments
Labels
BUG Issue type for reporting failure due to bug in functionality

Comments

@Alterrien
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Description

This is a follow-up to #1337.
Using our own fork based on master, we have recently switched to using Python3, and as such have had to move to Gunicorn. Because we rely on SQLAlchemy-based connectors, we have to limit the number of Gunicorn workers to 1 to prevent issues such as described in #3164.

This considerably degraded the performance of Hue to the point that even instances serving ~20 active users and rarely running more than 3 queries in parallel end up with timeouts and gets restarted. We'd like to go back to CherryPy as the code that allows to rely on CherryPy is still there, it just fails because of some Python2 breaking changes.
Thanks

Steps To Reproduce

Not Relevant

Logs

No response

Hue version

Open source current master

@Alterrien Alterrien added the BUG Issue type for reporting failure due to bug in functionality label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Issue type for reporting failure due to bug in functionality
Projects
None yet
Development

No branches or pull requests

1 participant