Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Promising results from DeepSeek R1 for code
11–20 of 765 posts
Re: Promising results from DeepSeek R1 for code
#12Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Is DeepSeek really that big of a deal that everyone else should worry?
Re: Promising results from DeepSeek R1 for code
#13Earlier quoted context omitted.
Is DeepSeek really that big of a deal that everyone else should worry?
A lot of the niceness about DeepSeek-R1's usage in coding is that you can see the thought process, which (IME) has been more useful than the final answer. It may well be that o1's chain of thought reasoning trace is also quite good. But they hide it as a trade secret and supposedly ban users for trying to access it, so it's hard to know.
Interestingly though, R1 struggled in part because it needed the value of some parameters I didn't provide, and instead it made an incorrect assumption about its value. This was apparent in the CoT trace, but the model didn't mention this in its final answer. If I wasn't able to see the trace, I'd not know what was lacking in my prompt, and how to make the model do better.
I presume OpenAI kept their traces a secret to prevent their competitors from training models with it, but IMO they strategically err'd in doing so. If o1's traces were public, I think the hype around DS-R1 would be relatively less (and maybe more limited to the lower training costs and the MIT license, and not so much its performance and usefulness.)
Re: Promising results from DeepSeek R1 for code
#14Earlier quoted context omitted.
Is DeepSeek really that big of a deal that everyone else should worry?
Yeah, it is definitely a big deal. I expect it will be a net positive: they proved that you can both train and run inference against powerful models for way less compute than people had previously expected - and they published enough details that other AI labs are already starting to replicate their results. I think this will mean cheaper, faster, and better models. This FAQ about it is very good: https://stratechery…
It is possible however that OpenAI was using similar level acceleration in the first place, they’ve just not published the details. And a few engineers left and replicated (or even bested it) in a new lab.
Overall, it’s a good boost, modern software is getting a better fit into new generation of hardware and is performing faster. Maybe we should pay more attention when NVIDIA is publishing their N-times faster ToPS numbers, and not completely dismissing it as marketing.
Re: Promising results from DeepSeek R1 for code
#15Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Is DeepSeek really that big of a deal that everyone else should worry?
Re: Promising results from DeepSeek R1 for code
#16Earlier quoted context omitted.
Is DeepSeek really that big of a deal that everyone else should worry?
Yeah, it is definitely a big deal. I expect it will be a net positive: they proved that you can both train and run inference against powerful models for way less compute than people had previously expected - and they published enough details that other AI labs are already starting to replicate their results. I think this will mean cheaper, faster, and better models. This FAQ about it is very good: https://stratechery…
Re: Promising results from DeepSeek R1 for code
#17Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Is DeepSeek really that big of a deal that everyone else should worry?
Re: Promising results from DeepSeek R1 for code
#18Re: Promising results from DeepSeek R1 for code
#19Earlier quoted context omitted.
Is DeepSeek really that big of a deal that everyone else should worry?
A lot of the niceness about DeepSeek-R1's usage in coding is that you can see the thought process, which (IME) has been more useful than the final answer. It may well be that o1's chain of thought reasoning trace is also quite good. But they hide it as a trade secret and supposedly ban users for trying to access it, so it's hard to know.
Re: Promising results from DeepSeek R1 for code
#20Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Is DeepSeek really that big of a deal that everyone else should worry?