mike31fr

[deleted]

Seems nice but I'm afraid it would not be compatible with my main work setup: VS Code on my main monitor, my web browser on my external monitor, and my eyes going back and forth between these 2 windows every few seconds to either read code or check the effects on the hot-reloading app. If one of the windows is dimmed, it would be painful.

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.

Got it, thank you!

Ok, the "View all" option in the dropdown is what I missed! Thanks!

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 ?

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

2. cat the file and see how much time it takes:

  time cat bigfile.txt

RESULTS:

- iterm2: 3.5s

- Default macOS terminal: 2.3s

- Ghostty: 1.8s

Have you ever experienced vim being slow? If so, would you know how I could reproduce this?

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?