Skip to content

Comments

Increase Uvicorn workers to 2#63

Merged
No767 merged 1 commit intomainfrom
noelle/increase-uvicorn-workers
Jul 22, 2025
Merged

Increase Uvicorn workers to 2#63
No767 merged 1 commit intomainfrom
noelle/increase-uvicorn-workers

Conversation

@No767
Copy link
Member

@No767 No767 commented Jul 22, 2025

Summary

The rationale is that one worker is not enough to handle everything, so having 2 workers per instance is a good stragety. The second worker is really only used to handle other requests, thus freeing up the resources needed for the first worker.

Types of changes

What types of changes does your code introduce to Kanae?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (Updates to README.md, the documentation, etc)
  • Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes. (if appropriate)
  • All workflows pass with my new changes
  • This PR does not address a duplicate issue or PR

@sonarqubecloud
Copy link

@No767 No767 merged commit 453ac60 into main Jul 22, 2025
14 checks passed
@No767 No767 deleted the noelle/increase-uvicorn-workers branch July 22, 2025 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant