-
Notifications
You must be signed in to change notification settings - Fork 1.8k
enh: Enable option in trtllm-bench build subcommand to avoid loading weights #4142
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
enh: Enable option in trtllm-bench build subcommand to avoid loading weights #4142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new CLI option to the trtllm-bench build subcommand that allows users to bypass loading actual checkpoint weights in favor of dummy weights for performance and debugging purposes.
- Introduces a new option (--no_weights_loading) to control whether weights are loaded.
- Sets a new "load_format" based on that option, and passes it to the engine-building function.
@kaiyux @LarryXFly can I get an approval for merge? |
dce2e94
to
210e1f2
Compare
/bot run --disable-fail-fast |
PR_Github #4927 [ run ] triggered by Bot |
PR_Github #4927 [ run ] completed with state |
210e1f2
to
2296855
Compare
2296855
to
efd230a
Compare
/bot run --disable-fail-fast |
PR_Github #5218 [ run ] triggered by Bot |
PR_Github #5218 [ run ] completed with state |
Signed-off-by: Venky <[email protected]>
Signed-off-by: Venky <[email protected]>
efd230a
to
cb3b6f7
Compare
/bot run --disable-fail-fast |
PR_Github #5349 [ run ] triggered by Bot |
PR_Github #5349 [ run ] completed with state |
/bot reuse-pipeline |
PR_Github #5398 [ reuse-pipeline ] triggered by Bot |
PR_Github #5398 [ reuse-pipeline ] completed with state |
PR title
Enable option in trtllm-bench build subcommand to avoid loading weights.
GitHub Bot Help
/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...
Provide a user friendly way for developers to interact with a Jenkins server.
Run
/bot [-h|--help]
to print this help message.See details below for each supported subcommand.
run [--disable-fail-fast --skip-test --stage-list "A10-1, xxx" --gpu-type "A30, H100_PCIe" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-[Post-Merge]-1, xxx"]
Launch build/test pipelines. All previously running jobs will be killed.
--disable-fail-fast
(OPTIONAL) : Disable fail fast on build/tests/infra failures.--skip-test
(OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.--stage-list "A10-1, xxx"
(OPTIONAL) : Only run the specified test stages. Examples: "A10-1, xxx". Note: Does NOT update GitHub check status.--gpu-type "A30, H100_PCIe"
(OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.--only-multi-gpu-test
(OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.--disable-multi-gpu-test
(OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.--add-multi-gpu-test
(OPTIONAL) : Force run the multi-GPU tests. Will also run L0 pre-merge pipeline.--post-merge
(OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.--extra-stage "H100_PCIe-[Post-Merge]-1, xxx"
(OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-[Post-Merge]-1, xxx".kill
kill
Kill all running builds associated with pull request.
skip
skip --comment COMMENT
Skip testing for latest commit on pull request.
--comment "Reason for skipping build/test"
is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.reuse-pipeline
reuse-pipeline
Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.