![]() |
|
tool calling reliability with PyTorch - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12) +--- Forum: Embedding / Reranking Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=53) +--- Thread: tool calling reliability with PyTorch (/showthread.php?tid=1259) Pages:
1
2
|
Re: tool calling reliability with PyTorch - tensorport - 10-19-2026 Quote:I tested this tonight. On B200 with Ollama, I saw basically the same behavior. The main thing that moved was latency, not quality. Good point. I ended up in about the same place using llama.cpp. Re: tool calling reliability with PyTorch - quantsupply - 10-19-2026 What worked for me was pretty simple. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Re: tool calling reliability with PyTorch - batchfield55 - 10-19-2026 Quote:What worked for me was pretty simple. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. A couple questions before I guess too hard. What model, what runtime, and roughly what context size? Re: tool calling reliability with PyTorch - llmpeak - 10-19-2026 worth checking the driver first. Re: tool calling reliability with PyTorch - macropilot - 10-19-2026 Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. |