Readit NewsRunning it on a MacBook with M1 Pro chip and 32 GB of RAM is quite slow. I expected to be as fast as phi4 but it's much slower.
With eval rate numbers:
- phi4: 12 tokens/s
- mistral-small: 9 tokens/s
On Nvidia RTX 4090 laptop:
- phi4: 36 tokens/s
- mistral-small: 16 tokens/s
Running it on a MacBook with M1 Pro chip and 32 GB of RAM is quite slow. I expected to be as fast as phi4 but it's much slower.
mike31fr commented on Promising results from DeepSeek R1 for code simonwillison.net/2025/Ja... · Posted by u/k__
Search for a GGUF on Hugging Face and look for a "use this model" menu, then click the Ollama option and it should give you something to copy and paste that looks like this:
ollama run hf.co/MaziyarPanahi/Mistral-7B-Instruct-v0.3-GGUF:IQ1_MGot it, thank you!
mike31fr commented on Promising results from DeepSeek R1 for code simonwillison.net/2025/Ja... · Posted by u/k__
This model is listed on ollama. The 20GB one is this one: https://ollama.com/library/deepseek-r1:32b-qwen-distill-q4_K...
Ok, the "View all" option in the dropdown is what I missed! Thanks!
mike31fr commented on Promising results from DeepSeek R1 for code simonwillison.net/2025/Ja... · Posted by u/k__
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 think through everything that needs to be updated.
Even if the code it writes has mistakes, the thinking helps spot bits of the code I may have otherwise forgotten to look at.
Noob question (I only learned how to use ollama a few days ago): what is the easiest way to run this DeepSeek-R1-Distill-Qwen-32B model that is not listed on ollama (or any other non-listed model) on my computer ?
Many people here seem impressed about speed/performance. I have been using all sorts of terminals / emulators over the past 20 years and it never occurred to me a terminal can be slow. When I type a command, I just get the result instantaneously, for any terminal. What are the use cases that can make a terminal be slow?
TESTED:
1. Create a file with 1 million lines:
for i in {1..1000000}; do echo "Line $i: This is a test of terminal performance."; done > bigfile.txt
time cat bigfile.txt
- iterm2: 3.5s
- Default macOS terminal: 2.3s
- Ghostty: 1.8s
Many people here seem impressed about speed/performance. I have been using all sorts of terminals / emulators over the past 20 years and it never occurred to me a terminal can be slow. When I type a command, I just get the result instantaneously, for any terminal. What are the use cases that can make a terminal be slow?
https://links.coinbase.com/s/vb/aKIVjNeDcGByosXohhDZZ7ijTHvh...