Would be great if the next generation of base models was designed to be inferred with 128GB of VRAM while 8bit quantized (which would fit in the consumer hardware class). For example, I imagine a strong MoE base with 16 billion active parameters and 6 or 7 experts would keep a good performance while being possible to run on 128GB RAM macbooks.
Run DeepSeek R1 Dynamic 1.58-bit
31–40 of 346 posts
Re: Run DeepSeek R1 Dynamic 1.58-bit
#32Flappy Bird in Python is the new Turing test
I also like to ask the models to create a simple basic Minecraft type game where you can break pieces and store them in your inventory, but disallow building stuff
Re: Run DeepSeek R1 Dynamic 1.58-bit
#33Thanks for the run instructions, unsloth. Deepseek is so new it's been breaking most of my builds.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#34It’s a very bold claim which is really shaking up the markets, so I can’t help but wonder if it was even verified at this point.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#35In general, how do you run these big models on cloud hardware? Do you cut them up layer-wise and run slices of layers on individual A100/H100s?
Then by using pipeline parallelism, if a new request comes, we simply stick them in a queue - GPUs 0, 1, 2, ..., 8. Request A is at GPU 2, Request B at GPU 1, Request C at GPU 0 and so on.
The other option is tensor parallelism were we split the weights evenly. You could combine pipeline and tensor parallelism as well!
Re: Run DeepSeek R1 Dynamic 1.58-bit
#36Earlier quoted context omitted.
While 192GB of ram is appealing, it's also quite expensive at $6000. For that price I rather buy a system with 5 used 3090s, which while being "only" 120GB of VRAM, you benefit from much faster tokens/s and prompt processing speed (the macs are notoriously slow at consuming large contexts).
Can I use that on the train though? I can with a 128GB MacBook, without it sounding like a helicopter taking off as well.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#37Random observation 1: I was running DeepSeek yesterday on my Linux with a RTX 4090 and I noticed that the models should fit into VRAM, which is 24GB. Or they are simply slow. So the Apple shared memory architecture has an advantage here. A 192GB Mx Ultra can load and process large models efficiently. Random observation 2: It's time to cancel the OpenAI subscription.
It seems that AMD Epyc CPUs support terabytes of ram, some are as cheap as 1000 EUR. why not just run the full R1 model on that - seems that it would be much cheaper than multiple of those insane NVidia-Karten.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#38Earlier quoted context omitted.
While 192GB of ram is appealing, it's also quite expensive at $6000. For that price I rather buy a system with 5 used 3090s, which while being "only" 120GB of VRAM, you benefit from much faster tokens/s and prompt processing speed (the macs are notoriously slow at consuming large contexts).
Can I use that on the train though? I can with a 128GB MacBook, without it sounding like a helicopter taking off as well.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#39I'm impressed by the 140 tokens per second speed with the 1.58-bit quantization running on dual H100s. That kind of performance makes the model practical for small or mid sized shops to use it for local applications. This is a huge win for people working on agents that require low latency that only local models could support.
Re: Run DeepSeek R1 Dynamic 1.58-bit
#40As someone who is out of the loop, what’s the verdict on R1? Was anyone able to reproduce the results yet? Is the claim that it only took $5M to train generally accepted? It’s a very bold claim which is really shaking up the markets, so I can’t help but wonder if it was even verified at this point.
Based on Nvidia being down 18% yesterday I would say the claim is generally accepted.