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

[serve] Deprecate system-level batching with warning, update the docs #14648

Merged
merged 13 commits into from
Mar 15, 2021

Conversation

edoakes
Copy link
Contributor

@edoakes edoakes commented Mar 12, 2021

Why are these changes needed?

Deprecates the existing system-level batching codepath and instead recommends @serve.batch. The old codepath will still work after this PR, but print a warning pointing at the docs for the new workflow.

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Copy link
Contributor

@architkulkarni architkulkarni left a comment

Choose a reason for hiding this comment

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

Looks great, thanks for the careful doc update! No major comments

doc/source/serve/architecture.rst Outdated Show resolved Hide resolved
doc/source/serve/architecture.rst Outdated Show resolved Hide resolved
doc/source/serve/core-apis.rst Outdated Show resolved Hide resolved
doc/source/serve/ml-models.rst Outdated Show resolved Hide resolved
doc/source/serve/performance.rst Outdated Show resolved Hide resolved
doc/source/serve/tutorials/batch.rst Outdated Show resolved Hide resolved
seconds to wait for a full batch to arrive. The default wait is ``0s`` to
minimize query latency. You can increase the timeout to improve throughput
and increase utilization at the cost of some additional latency.
By default, Ray Serve performs *opportunistic batching*. This means that as
Copy link
Contributor

Choose a reason for hiding this comment

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

This note was the most useful piece of the documentation for me when I was first reading it (though maybe it's very standard and not that useful to others). Is there a way to make it more prominent/move it higher up without disrupting the flow?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it might be fine to just put it all the way at the top after the top-level description of how to do batching. Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I moved it just after the initial code sample, I think that's an improvement. Any earlier is probably confusing. LMK what you think.

edoakes and others added 5 commits March 12, 2021 11:37
Co-authored-by: architkulkarni <architkulkarni@users.noreply.github.com>
Co-authored-by: architkulkarni <architkulkarni@users.noreply.github.com>
Co-authored-by: architkulkarni <architkulkarni@users.noreply.github.com>
Co-authored-by: architkulkarni <architkulkarni@users.noreply.github.com>
@edoakes
Copy link
Contributor Author

edoakes commented Mar 12, 2021

Thanks for the review @architkulkarni. Addressed the comments, please have another look.

Copy link
Contributor

@architkulkarni architkulkarni left a comment

Choose a reason for hiding this comment

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

Changes look good, thanks!

@edoakes edoakes merged commit d90cd54 into ray-project:master Mar 15, 2021
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