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

CV2-5726 don't use reload flag when running the server in the cloud #133

Merged
merged 3 commits into from
Dec 2, 2024

Conversation

DGaffney
Copy link
Collaborator

Description

We use --reload when we really shouldn't in production on Presto - it slows requests down and the server will, by definition, never reload.

Reference: CV2-5726

How has this been tested?

Not tested locally, by definition, since this applies to prod

Are there any external dependencies?

None

Have you considered secure coding practices when writing this code?

None

Copy link
Contributor

@skyemeedan skyemeedan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a great change! I'm assuming we will know right away in QA if the performance changed oddly

@@ -1,10 +1,14 @@
.PHONY: run run_http run_worker run_test
.PHONY: run run_http run_worker run_processor run_test
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change is just about the build order for make, right?

Makefile Outdated

run:
./start_all.sh

run_http:
ifeq ($(filter $(DEPLOY_ENV),qa live),)
uvicorn main:app --host 0.0.0.0 --reload
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the --reload flag is about reloading based on code monitoring right? Assuming uvicorn will still try to restart without the flag?

@DGaffney DGaffney merged commit 57ef2b6 into master Dec 2, 2024
2 checks passed
@DGaffney DGaffney deleted the cv2-5726-no-reloads-on-cloud branch December 2, 2024 13:59
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.

2 participants