Ace
Ace
somewhat looking into this and I found this bit of logic to the first thing: I also noticed this part: However, I do not know if I myself would be...
This wording is arguably bad > Alpaca will also start a new ollama instance as a child of itself, which makes the memory usage worse I meant to say that...
I had a thought about possible solutions. Instead of ollama being a child process, start it as a daemon. If ollama doesn't have contact with alpaca after n minutes it...
rip: `Device id=0xc08b, name=G502 Hero - is not supported yet!`
I'll look into it, but I need sleep first