[None][feat] support calling gc.freeze#13907
Closed
ixlmar wants to merge 1 commit intoNVIDIA:mainfrom
Closed
Conversation
Collaborator
Author
|
/bot run |
Collaborator
|
PR_Github #47400 [ run ] triggered by Bot. Commit: |
Collaborator
|
PR_Github #47400 [ run ] completed with state
|
Signed-off-by: ixlmar <206748156+ixlmar@users.noreply.github.com>
Collaborator
Author
|
Change provides no performance advantage over #13910. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
LlmArgs.garbage_collection_freeze_after_initoption (for LLM worker) andTRTLLM_SERVER_FREEZE_GCenvironment variable (fortrtllm-serveprocess). These settings enable the invocation ofgc.freezeupon startup, which avoids latency spikes caused by repeated attempts to garbage collect long-lived resources. The tradeoff here is that all objects alive at the time of thegc.freezecall will be excluded from garbage collection, such that the resources associated with any objects that are abandoned later on (e.g. buffers which are replaced by larger buffers) will effectively leak. However, such leakage remains bounded.Test Coverage
n/a (beta)
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.