Repository navigation
feat(compile): expose joint backend and bucket settings - #15
Open
yu-chen-code wants to merge 2 commits into
Open
yu-chen-code wants to merge 2 commits into
yu-chen-code wants to merge 2 commits into
Conversation
yu-chen-code
force-pushed
the
feat-graph-backend-config
branch
from
November 9, 2026 11:25
81212ce to
11a9f2f
Compare
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.
What type of PR is this?
/kind feature
What does this PR do / why do we need it:
Refreshed on 2026-11-09 against fork/upstream master
a6be99d3. PR1421 is now merged upstream, so its duplicate prerequisite has been removed. Current head:11a9f2f9ca53d0706b06648ff2b02149696c8131; retained feature/dependency commits:d7d0c09e,11a9f2f9. Git range-diff confirms unchanged feature patches. Focused CPU regression on this exact head: 197 JUnit records, 2 failures, 0 errors. The two existing CPU Inductor strict-equality failures remain recorded. The isolated refresh environments now include master-required PEFT 0.21.2 and accelerate 1.13.0; pip check passes. All numerical runs and older source hashes below are pre-refresh evidence. NPU precision training and formal upstream CI were not rerun for this rebase.Let TextTrainer's joint-graph configuration select the existing terminal Inductor and FSDP bucketing passes explicitly, and keep backend input metadata consistent with physical parameter storage.
inductor_mode/inductor_configsandfsdp_bucketing/fsdp_bucket_modulesfields to CompileConfig, validate them and project them into PassConfig. Defaults retain FX execution and disabled bucketing. Existing decoderbackend/mode/optionskeep their separate meaning.Validation uses deploy32, Python3.12.13, Torch2.15.0.dev20261005+cpu and torch-npu2.15.0:
0.701689600944519versus0.7016897201538086, two FP32 ULPs). The assertions are unchanged and no all-tests-passed result is claimed.LoweringException: no scheduling registered for device npu. This Torch build has no NPU Inductor scheduler. The distinctnpuDynamo registration also warns that it is an eager implementation without torchair; it is not used as backend-compilation evidence. NPU Inductor acceptance remains open.Reproduction:
Source manifests, raw failures, unchanged-baseline comparisons and numerical receipts are retained under T020
runs/20261106-graph-capability-spikes. Full DSV4.1 lowering and performance gains are not claimed.Which issue(s) this PR fixes:
None.
Code review checklist [illustration]: