Qwen/Qwen3.5-397B-A17B
Image-Text-to-Text
•
403B
•
Updated
•
46.8k
•
•
645
Ron PRO
ronedgecomb
AI & ML interests
Motion & Graphic Designer | Developer
Recent Activity
liked
a model
1 day ago
Qwen/Qwen3.5-397B-A17B
liked
a model
4 days ago
Qwen/Qwen3-ASR-1.7B
liked
a model
4 days ago
circlestone-labs/Anima
Organizations
None yet
liked
a
model
1 day ago
liked
3
models
4 days ago
liked
a
model
8 days ago
liked
a
model
14 days ago
upvoted
an
article
18 days ago
Article
Make your ZeroGPU Spaces go brrr with ahead-of-time compilation
- +2
•
75
liked
4
models
18 days ago
ibm-granite/granite-vision-3.3-2b
Image-to-Text
•
3B
•
Updated
•
42.7k
•
71
tencent/HunyuanImage-3.0-Instruct
Image-to-Image
•
83B
•
Updated
•
1.38k
•
•
357
moonshotai/Kimi-K2.5
Image-Text-to-Text
•
171B
•
Updated
•
895k
•
•
2.24k
arcee-ai/Trinity-Large-Preview
Text Generation
•
Updated
•
1.8k
•
142
liked
4
models
20 days ago
reacted to
ovi054's
post with ❤️
21 days ago
Post
2972
ovi054/LTX-2-19b-Squish-LoRA ⚡
I trained a Squish LoRA for LTX-2. Upload an image and give prompt "squish it" to get the squish video.
Demo output videos are attached.
👉Try it now:
ovi054/LTX-2-19b-Squish-LoRA
ovi054/ltx-2-Audio-to-Video
I trained a Squish LoRA for LTX-2. Upload an image and give prompt "squish it" to get the squish video.
Demo output videos are attached.
👉Try it now:
ovi054/LTX-2-19b-Squish-LoRA
ovi054/ltx-2-Audio-to-Video
reacted to
IlyasMoutawwakil's
post with 🔥
21 days ago
Post
3010
Transformers v5 just landed! 🚀
It significantly unifies and reduces modeling code across architectures, while opening the door to a whole new class of performance optimizations.
My favorite new feature? 🤔
The new dynamic weight loader + converter. Here’s why 👇
Over the last few months, the core Transformers maintainers built an incredibly fast weight loader, capable of converting tensors on the fly while loading them in parallel threads. This means we’re no longer constrained by how parameters are laid out inside the safetensors weight files.
In practice, this unlocks two big things:
- Much more modular modeling code. You can now clearly see how architectures build on top of each other (DeepSeek v2 → v3, Qwen v2 → v3 → MoE, etc.). This makes shared bottlenecks obvious and lets us optimize the right building blocks once, for all model families.
- Performance optimizations beyond what torch.compile can do alone. torch.compile operates on the computation graph, but it can’t change parameter layouts. With the new loader, we can restructure weights at load time: fusing MoE expert projections, merging attention QKV projections, and enabling more compute-dense kernels that simply weren’t possible before.
Personally, I'm honored to have contributed in this direction, including the work on optimizing MoE implementations and making modeling code more torch-exportable, so these optimizations can be ported cleanly across runtimes.
Overall, Transformers v5 is a strong signal of where the community and industry are converging: Modularity and Performance, without sacrificing Flexibility.
Transformers v5 makes its signature from_pretrained an entrypoint where you can mix and match:
- Parallelism
- Quantization
- Custom kernels
- Flash/Paged attention
- Continuous batching
- ...
Kudos to everyone involved! I highly recommend the:
Release notes: https://github.com/huggingface/transformers/releases/tag/v5.0.0
Blog post: https://huggingface.co/blog/transformers-v5
It significantly unifies and reduces modeling code across architectures, while opening the door to a whole new class of performance optimizations.
My favorite new feature? 🤔
The new dynamic weight loader + converter. Here’s why 👇
Over the last few months, the core Transformers maintainers built an incredibly fast weight loader, capable of converting tensors on the fly while loading them in parallel threads. This means we’re no longer constrained by how parameters are laid out inside the safetensors weight files.
In practice, this unlocks two big things:
- Much more modular modeling code. You can now clearly see how architectures build on top of each other (DeepSeek v2 → v3, Qwen v2 → v3 → MoE, etc.). This makes shared bottlenecks obvious and lets us optimize the right building blocks once, for all model families.
- Performance optimizations beyond what torch.compile can do alone. torch.compile operates on the computation graph, but it can’t change parameter layouts. With the new loader, we can restructure weights at load time: fusing MoE expert projections, merging attention QKV projections, and enabling more compute-dense kernels that simply weren’t possible before.
Personally, I'm honored to have contributed in this direction, including the work on optimizing MoE implementations and making modeling code more torch-exportable, so these optimizations can be ported cleanly across runtimes.
Overall, Transformers v5 is a strong signal of where the community and industry are converging: Modularity and Performance, without sacrificing Flexibility.
Transformers v5 makes its signature from_pretrained an entrypoint where you can mix and match:
- Parallelism
- Quantization
- Custom kernels
- Flash/Paged attention
- Continuous batching
- ...
Kudos to everyone involved! I highly recommend the:
Release notes: https://github.com/huggingface/transformers/releases/tag/v5.0.0
Blog post: https://huggingface.co/blog/transformers-v5
- 3 replies
liked
a
model
27 days ago
upvoted
2
collections
27 days ago