[LTX-2] Run Gemma-3 Text Encoder natively in JAX via TorchAX#398
Open
[LTX-2] Run Gemma-3 Text Encoder natively in JAX via TorchAX#398
Conversation
13e195e to
7707c3d
Compare
7707c3d to
252c34e
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.
Description
This PR transitions the LTX-2 pipeline's text encoding process to utilize TorchAX, bridging the Gemma-3 model natively into JAX and significantly optimizing memory usage to prevent TPU out-of-memory errors. Minor PyLint warnings across the pipeline were also resolved during the refactor.
Key changes include:
TorchaxGemma3TextEncoder. TPU sharding is now manually distributed across the batch dimension viajax.device_putto prevent Softmax OOM crashes.batch_size > 2, HBM crashes during decoding are avoided.Benchmarks
Performance comparison demonstrating latency improvements from TorchAX integration.