![]() |
|
human evals on small teams - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Evaluation & Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=16) +--- Forum: Evals (https://www.datasculpting.ai/inference/forumdisplay.php?fid=66) +--- Thread: human evals on small teams (/showthread.php?tid=857) Pages:
1
2
|
human evals on small teams - fusedtinker - 10-08-2026 This keeps coming up in conversation so I figured I'd start a thread. It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with KV cache pressure. Wondering if this is just where the whole space is heading now. My use case is pretty ordinary: local chat, some document work, and occasional batch jobs. Re: human evals on small teams - fastlab - 10-08-2026 Quote:This keeps coming up in conversation so I figured I'd start a thread. My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Llama and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. Re: human evals on small teams - macrostack69 - 10-08-2026 A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at KV cache pressure. Once you know the plain path works, then add the faster path back in piece by piece. Re: human evals on small teams - lablab - 10-08-2026 Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt? Re: human evals on small teams - audioforge - 10-08-2026 Quote:Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt? Thanks, that helps. I ended up in about the same place using Ollama. The biggest change for me was simplifying the stack instead of adding one more optimization layer. There are a few different conversations hiding inside this thread, so being explicit about the goal helps. Re: human evals on small teams - thetaarch43 - 10-08-2026 Interesting, I hadn't tried that. That matches what I saw on dual 3090. Re: human evals on small teams - routeforge64 - 10-10-2026 Interesting, I hadn't tried that. That matches what I saw on dual 3090. Re: human evals on small teams - amberhall - 10-10-2026 Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one. Re: human evals on small teams - macrostack69 - 10-13-2026 What exact setup are you running? What model, what runtime, and roughly what context size? Re: human evals on small teams - cudacrate - 10-13-2026 A couple questions before I guess too hard. Is this local-only or are you routing anything externally? |