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

docs: Load new model version should not reload loaded existing model version(s) #7537

Closed
wants to merge 1 commit into from

Conversation

kthui
Copy link
Contributor

@kthui kthui commented Aug 16, 2024

What does the PR do?

Document any loaded and unmodified model version(s) will not be reloaded upon changes to other model versions.

Checklist

  • PR title reflects the change and is of format <commit_type>: <Title>
  • Changes are described in the pull request.
  • Related issues are referenced.
  • Populated github labels field
  • Added test plan and verified test passes.
  • Verified that the PR passes existing CI.
  • Verified copyright is correct on all changed files.
  • Added succinct git squash message before merging ref.
  • All template sections are filled out.
  • Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

  • build
  • ci
  • docs
  • feat
  • fix
  • perf
  • refactor
  • revert
  • style
  • test

Related PRs:

#7527
triton-inference-server/core#388

Where should the reviewer start?

Start with the core PR.

Test plan:

This is a documentation change, so any testing will be covered by related PRs linked.

  • CI Pipeline ID: 17511909

Caveats:

N/A

Background

N/A

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

N/A

@@ -236,6 +236,11 @@ in-flight sequence(s) will be routed to the same model instance for processing.
It is currently the responsibility of the user to ensure any in-flight
sequence(s) are completed before reloading a sequence model.

* Starting from r24.09, if the version policy on the model configuration is
Copy link
Contributor

Choose a reason for hiding this comment

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

how difficult is it to provide an example?

No fault here - but I don't quite follow the change / not sure others would understand.

If it's already considered 'expected' behavior - maybe we can just update the descriptions below ...

@kthui
Copy link
Contributor Author

kthui commented Aug 16, 2024

Discussed offline that we are ok with not having a docs for this change, because not reloading an unchanged model version is expected and this change can be mentioned in the release note, so closing this PR.

@kthui kthui closed this Aug 16, 2024
@kthui kthui deleted the jacky-load-new-model-version-docs branch October 22, 2024 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: docs Documentation only changes
Development

Successfully merging this pull request may close these issues.

2 participants