implement qat and weight sharing#1593
Open
kiratoyoshihara wants to merge 1 commit intoopenai:mainfrom
Open
Conversation
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.
Note: This is a draft PR.
Approach Overview
To achieve extreme efficiency under the 16MB artifact constraint and the 10-minute training limit on 8xH100, I am introducing a custom architecture modifying the baseline
train_gpt.py.1. Depth Recurrence (Parameter Tying)
Standard transformer architectures can only hold a few million parameters within 16MB. To overcome this, I have replaced the standard
nn.ModuleListof blocks with a single shared Transformer Block. By applying this block recursively across all layers, we simulate a much deeper network and maximize representational capacity without increasing the actual file size on disk.2. Quantization-Aware Training (QAT)
To cram the maximum effective parameter count into the footprint, I implemented a Fake Quantization step (symmetric INT8 via Straight-Through Estimator) inside
CastedLinear. The forward/backward passes are kept in high precision (bfloat16) for H100 throughput, but the weights are regularized to be robust to extreme post-training quantization.Current Status
train_gpt.pyI will update this PR with training logs and the final artifact once the large-scale runs are complete.