joebarbere 2 days ago

Thanks for this! I've been trying to get local training working on Fedora with ROCm for a while now, and this is the first project that ran end-to-end on my RX 7600 XT 16GB.

The whole reason for me buying the card was to play around with deep learning and models, so it's awesome to have a stepping off point now!

No CUDA meant ROCm surprisingly just worked with JAX.

Gotchas for anyone with a 7600 XT: it needed two env vars, HSA_OVERRIDE_GFX_VERSION=11.0.0 because JAX's plugin rejects gfx1102, and XLA_FLAGS=--xla_gpu_enable_triton_gemm=false to stop a GPU hang.

I'm on Fedora 45 with the in-kernel amdgpu driver, rootless podman and AMD's rocm/jax image (ROCm 10.1, JAX 0.11.1). Nothing ROCm is installed on the host, which is nice.

Container setup is in a PR if it helps anyone: https://github.com/Vaibhaav-Tiwari/deepseek-v3-jax/pull/1

  • kouteiheika 1 day ago

    > Gotchas for anyone with a 7600 XT: it needed two env vars, HSA_OVERRIDE_GFX_VERSION=11.0.0 because JAX's plugin rejects gfx1102, and XLA_FLAGS=--xla_gpu_enable_triton_gemm=false to stop a GPU hang.

    It's sad that after so many years AMD's software support is still atrocious for non-datacenter hardware, and their short-sighted management still doesn't see it as a priority to fix. This is costing them sales, but I guess they only care about selling to hyperscalers.

    • genxy 1 day ago

      Why they don't understand is that this materially impacts them because it blocks the dev funnel. It is absolutely confounding how AMD refuses to realize this for decades.

  • VaibhaavTiwari 1 day ago

    Thanks Joe, this is great. Reviewed and tested what I could without an AMD card, and merged the PR!

armcat 2 days ago

I love this, there is nothing like recreating a model from first principles, plus makes me want to revisit Jax again (I'll do it after I spend enough time with Zig). Thanks for this!

mattfrommars 2 days ago

Post like these always drives a motivation to understand how inference or what OP did.

For folks who are more familiar in this space, is there a good road map how to build and understand the intuition behind this? I’m comfortable in Java and Python and do vanilla SWE work.

nico 2 days ago

> to asking a language model to create a 3D end-to-end working model for me to capture the nuances

Love this! Yes, having a visual of the system makes it a lot easier to reason about and understand

I wish all AI models came with interactive animated workflows of their architecture

> so I wanted it to be different just for the sake of it and used various books by…

That’s cool and great for your own project. At the same time it helps to use datasets that others have used, because then you can compare results more directly

Excellent write up, I really appreciate all the detail and the sample outputs at the end. Excited to see what I could apply for this to the small <10M models I’ve been training

  • VaibhaavTiwari 1 day ago

    that's true, I'll try to incorporate standard datasets when the goal would be comparison. the detective dataset was just for fun :)

d_tr 1 day ago

I am just starting Raschka's book to write an llm from scratch in C++ with zero dependencies with avx-512 on a 9950x, and then I'd like to go through the literature for more advanced stuff.

I don't know what Jax is exactly but while I am aware that the algorithm implementation is not something terribly complicated, 200 lines still sounds impressive.

If anyone wants to share any tips, they're welcome.

  • VaibhaavTiwari 1 day ago

    you can think of JAX as numpy with automatic gradients and a compiler so no backward pass or going into kernels was needed. also, Raschka's book is excellent! you should also check out his model comparison primer that's awesome + you can go on to https://jax-ml.github.io/scaling-book/ next

    • d_tr 1 day ago

      Thanks, I will definitely check these out!

try-working 1 day ago

Could you build and train a V4.1 the same way?

  • VaibhaavTiwari 1 day ago

    Surely that can be tried! of course at a small scale if you're short on GPUs. what I understand is that V4 replaces MLA with a hybrid of two compressed attention types and changes the residual connections, while keeping the mixture-of-experts design, but I haven't gone in-depth architecture :)

steeve 1 day ago

fun nugget: if you grab our (zml) PJRT Metal plugin and point JAX to it, it should just work

  • VaibhaavTiwari 1 day ago

    Oh nice, didn't know that! Will give it a try, thanks!

madduci 1 day ago

Does this work on CPU only hardware (Intel Core Ultra 7)?

  • VaibhaavTiwari 1 day ago

    Yes of course! it’s plain JAX, so it runs on any CPU, you just gotta make a few changes cause this one is for Apple Metal

    • madduci 1 day ago

      I mean, performance wise

      • akutlay 13 hours ago

        Don’t expect much

vivzkestrel 1 day ago

anyone got a c++ version of this?

  • VaibhaavTiwari 1 day ago

    I dont think one's available as of now but you can check out llama.cpp, though they run them for real weights rather than small build-from-scratch versions like this!

itsthecourier 1 day ago

thank you so so much for writing this, I will recreate it for learning

VaibhaavTiwari 2 days ago

I wanted to understand what actually makes DeepSeek V3 different, so I rebuilt its three main ideas from scratch in pure JAX: Multi-head Latent Attention, mixture-of-experts with bias-based load balancing instead of an auxiliary loss, and multi-token prediction. The model is about 190 lines.

It’s a 36.2M-parameter version trained on a MacBook Air M5 (24 GB) with jax-metal, on 207 old detective novels. 12,000 steps took about 2.6 hours.

Full write-up with diagrams and results: https://vaibhaav.in/writing/deepseek-v3-jax/

The trained checkpoint and exact data are in the v1.0 release, so you can generate text without training.

Would love corrections if I got anything wrong :)

  • wg0 2 days ago

    This is very illustrative. I'm sure a great learning experience for you but so much more for so many others.

    Respect and thanks.

  • DoctorOetker 21 hours ago

    could you add a disclaimer about which facets are missing (ignoring the parameter count)? the way the title is phrased seems to promise a more compact but an otherwise equivalent code, but in reality there is the risk that the rewrite has unintentional functional regressions in case you oversaw the importance of certain parts of the original codebase.

    What would such an overview look like? a fork of DS-V3 with "// reimplemented" markers so any non-reimplemented lines can be identified?