0

I ssh into my dev machine, and then start a download, for instance "ollama pull llama3"

This uses all of the available bandwidth for the network interface, which makes ssh unresponsive until the download completes.

Is there a way to reserve some amount of bandwidth for ssh?

I've tried the "trickle" utility, e.g. "trickle -s -d 200 ollama pull llama3", but that did not have any effect.

Improve this question
7
  • 2
    That doesn't sound right at all. What kind of connection is in use – Wifi? ADSL? Does the SSH session become completely unresponsive or only mostly?
    – grawity_u1686
    Commented May 29 at 9:32
  • 1 Gigabit Ethernet, then fiber. "Mostly unresponsive" would cover it, there are no progress updates from the download, but can get a ctrl-c trough.
    – Morten
    Commented May 29 at 9:52
  • I totally don't know ollama pull. Does it pass the job to some background downloader and return immediately? If not, i.e. if it downloads in the foreground, then it's normal you cannot interact with the parent shell until the download completes and the foreground child process exits.
    – Kamil Maciorowski
    Commented May 29 at 9:54
  • It runs in the foreground and prints download status output, but it might hand of the download to a background process. But that's a bit beside the point, other ssh sessions to the same machine are affected as well.
    – Morten
    Commented May 29 at 9:55
  • 1
    Yeah, I would say that's definitely not normal for Ethernet – does it also happen when you download anything else (or run an iperf3 test), or is it specifically just Ollama?
    – grawity_u1686
    Commented May 29 at 10:49

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .