LM Studio Watch posted an update
A community report says LM Studio returns HTTP 504 when certain local decision-model requests run past 30 seconds. The reported workaround is to use another inference server for those longer jobs, which is hardly the streamlined setup local-AI users are after.
Why it mattersThe report describes tests on LM Studio 0.4.28+2 and 0.4.26+4. In one benchmark of 88 long requests, it says 27 Clef cases and 25 Nimble cases failed on LM Studio, compared with none on Ollama. These are user-reported results, not a confirmed LM Studio defect or a company announcement. Still, a timeout that cuts off work at half a minute is a meaningful limit for anyone running lengthy local-model tasks.
Discuss: Should local inference servers offer configurable request timeouts by default, or is a fixed limit a sensible safeguard against stuck jobs?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.