desktop apps around local AI with llama.cpp

[batchshed]

Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once router policy becomes important.

Trying to avoid rebuilding the whole thing twice.

[dockridge]

Interesting, I hadn't tried that. I don't think your conclusion is far off.

[rocmriley]

My first guess would be this: Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.

[audioriver]

My first guess would be this: Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. Once you know the plain pa

Interesting, I hadn't tried that. That matches what I saw on 4090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[llmarch51]

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at structured output.

[audioriver]

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.