bartowski/LatitudeGames_Equinox-31B-GGUF
Image-Text-to-Text • 31B • Updated • 10k • 6
Digital Spellcaster
DigitalSpellcaster
AI & ML interests
Primary interest is models for my Pixel 10 Pro
Recent Activity
liked a model 6 days ago
bartowski/LatitudeGames_Equinox-31B-GGUF upvoted a collection 6 days ago
Gemma4 PRISM published a bucket 8 days ago
DigitalSpellcaster/ThisIsABucketOrganizations
None yet
liked a
model 6 days ago
upvoted a collection 6 days ago
published a
bucket 8 days ago
upvoted a collection about 1 month ago
liked 3
models about 1 month ago
I would be interested in some more NVF4P Quants
4
#2 opened 2 months ago
by DigitalSpellcaster
upvoted a collection 2 months ago
liked 2
models 2 months ago
upvoted 2
collections 2 months ago
liked a
model 4 months ago
upvoted a collection 4 months ago
reacted to IlyasMoutawwakil's post with 🔥 4 months ago
Post
2474
After 2 months of refinement, I'm happy to announce that a lot of Transformers' modeling code is now significantly more torch-compile & export-friendly 🔥
Why it had to be done 👇
PyTorch's Dynamo compiler is increasingly becoming the default interoperability layer for ML systems. Anything that relies on torch.export or torch.compile, from model optimization to cross-framework integrations, benefits directly when models can be captured as a single dynamo-traced graph !
Transformers models are now easier to:
⚙️ Compile end-to-end with torch.compile backends
📦 Export reliably via torch.export and torch.onnx.export
🚀 Deploy to ONNX / ONNX Runtime, Intel Corporation's OpenVINO, NVIDIA AutoDeploy (TRT-LLM), AMD's Quark, Meta's Executorch and more hardware-specific runtimes.
This work aims at unblocking entire TorchDynamo-based toolchains that rely on exporting Transformers across runtimes and accelerators.
We are doubling down on Transformers commitment to be a first-class citizen of the PyTorch ecosystem, more exportable, more optimizable, and easier to deploy everywhere.
There are definitely some edge-cases that we still haven't addressed so don't hesitate to try compiling / exporting your favorite transformers and to open issues / PRs.
PR in the comments ! More updates coming coming soon !
Why it had to be done 👇
PyTorch's Dynamo compiler is increasingly becoming the default interoperability layer for ML systems. Anything that relies on torch.export or torch.compile, from model optimization to cross-framework integrations, benefits directly when models can be captured as a single dynamo-traced graph !
Transformers models are now easier to:
⚙️ Compile end-to-end with torch.compile backends
📦 Export reliably via torch.export and torch.onnx.export
🚀 Deploy to ONNX / ONNX Runtime, Intel Corporation's OpenVINO, NVIDIA AutoDeploy (TRT-LLM), AMD's Quark, Meta's Executorch and more hardware-specific runtimes.
This work aims at unblocking entire TorchDynamo-based toolchains that rely on exporting Transformers across runtimes and accelerators.
We are doubling down on Transformers commitment to be a first-class citizen of the PyTorch ecosystem, more exportable, more optimizable, and easier to deploy everywhere.
There are definitely some edge-cases that we still haven't addressed so don't hesitate to try compiling / exporting your favorite transformers and to open issues / PRs.
PR in the comments ! More updates coming coming soon !
- 1 reply