[LLM:Bugfix] Fix QNN export chunk-size and per-task workdir handling#4611
Merged
Conversation
Qxinyu
approved these changes
Jul 15, 2026
Contributor
Author
|
thanks your review. |
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
This PR contains two small bug fixes in the LLM QNN export path.
1. Honor
--chunk_sizewhen generating prefill IOtransformers/llm/export/npu/generate_llm_qnn.pyexposed--chunk_size, butconvert_llm()always called:This meant the prefill QNN graph could still be generated against 128-token IO even when
--chunk_size 256/512was requested.2. Run QNN compile subprocesses inside the per-task workdir
source/backend/qnn/npu_convert.pyinvoked the compile subprocess without settingcwd=workdir.For parallel conversions, this could make multiple tasks share the same process working directory assumptions and increase the chance of temporary/output path collisions.
Why this matters
In the MNN QNN offline export path, these issues can make generated artifacts inconsistent with runtime expectations:
chunk_limitsand generated graphs may divergeppl_evalresults can become misleadingModule
LLM
Type
Checklist
[Module:Type] DescriptionformatFixed
#4612