You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading Connexion to version 3.x, we are encountering significant CPU spikes during deployments. The spikes normalize shortly after deployment but consume approximately 10x more CPU compared to our previous version. This occurs consistently across multiple deployment attempts, as illustrated in the attached image.
Expected behaviour
The deployment should proceed with minimal CPU usage, similar to previous Connexion versions.
Actual behaviour
CPU usage spikes drastically during deployment.
CPU consumption returns to normal shortly after deployment is complete.
The spikes occur during every deployment attempt.
Additional info:
Environment Details
In the following snippet we can see the updated libraries
And in below I have added the current app configurations
Description
After upgrading Connexion to version 3.x, we are encountering significant CPU spikes during deployments. The spikes normalize shortly after deployment but consume approximately 10x more CPU compared to our previous version. This occurs consistently across multiple deployment attempts, as illustrated in the attached image.
Expected behaviour
The deployment should proceed with minimal CPU usage, similar to previous Connexion versions.
Actual behaviour
CPU usage spikes drastically during deployment.
CPU consumption returns to normal shortly after deployment is complete.
The spikes occur during every deployment attempt.
Additional info:
Environment Details
In the following snippet we can see the updated libraries
And in below I have added the current app configurations
app setup
main function
docker configs
And running the docker using the gunicorn
gunicorn -c gunicorn-config-docker.py middleware:connexion_app
Given the above information we appreciate any insights or guidance on resolving this issue.
Thank you!
The text was updated successfully, but these errors were encountered: