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

[SkyServe] Update Documentation #3022

Merged
merged 11 commits into from
Jan 27, 2024
Merged

[SkyServe] Update Documentation #3022

merged 11 commits into from
Jan 27, 2024

Conversation

MaoZiming
Copy link
Collaborator

Tested (run the relevant ones):

  • Code formatting: bash format.sh
  • Any manual or new tests for this PR (please specify below)
  • All smoke tests: pytest tests/test_smoke.py
  • Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
  • Backward compatibility tests: bash tests/backward_comaptibility_tests.sh

@MaoZiming MaoZiming marked this pull request as ready for review January 24, 2024 17:26
Copy link
Collaborator

@cblmemo cblmemo left a comment

Choose a reason for hiding this comment

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

Thanks for adding the doc!! Left several comments ;)

docs/source/serving/update.rst Outdated Show resolved Hide resolved
docs/source/serving/update.rst Outdated Show resolved Hide resolved
docs/source/serving/update.rst Show resolved Hide resolved
docs/source/serving/update.rst Show resolved Hide resolved

$ sky serve update http-server examples/serve/http_server/task.yaml

SkyServe will first launch two new replicas with 4 CPUs. When the number of new replicas reaches the ``min_replicas`` (i.e., 2) required for the service, SkyServe will scale down old replicas to save cost. The service's version is updated from 1 to 2. The replicas with ID 3 and 4 are the new replicas with 4 CPUs. The replicas with ID 1 and 2 are the old replicas with 2 CPUs. When the new replicas are still provisioning, SkyServe will only send traffic to the old replicas.
Copy link
Collaborator

Choose a reason for hiding this comment

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

give a workaround for quota issue? e.g. update to 0 replicas first and the update to the desired number of replicas

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This seems rather complicated. I don't think we should mention them on the doc -- rather keeping a todo to look into in the future.

docs/source/serving/update.rst Show resolved Hide resolved
docs/source/serving/update.rst Outdated Show resolved Hide resolved
docs/source/serving/update.rst Outdated Show resolved Hide resolved
Copy link
Collaborator

@cblmemo cblmemo left a comment

Choose a reason for hiding this comment

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

The contents look great to me ;) cc @concretevitamin for a look on wording and expression

docs/source/serving/update.rst Outdated Show resolved Hide resolved
docs/source/serving/update.rst Outdated Show resolved Hide resolved
@MaoZiming MaoZiming merged commit 0af0b1b into master Jan 27, 2024
19 checks passed
@MaoZiming MaoZiming deleted the serve-update-doc branch January 27, 2024 16:44
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.

None yet

3 participants