JAX for inference only with LM Studio

[mangowire]

Did a bit of testing and thought I'd post the result here.

Short version: TensorRT-LLM behaved well for me, but only after I stopped ignoring NVFP4.

Curious if anyone else landed in the same place.

[northcraft90]

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. Once you know the plain path works, then add the faster path back in piece by piece.

[southden]

That matches what I was seeing. I ended up in about the same place using SGLang. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[macrostack69]

Did a small comparison this afternoon. On B200 with vLLM, I saw basically the same behavior. I expected the model choice to matter more than it did.

[cudacrate]

Did a small comparison this afternoon. On B200 with vLLM, I saw basically the same behavior. I expected the model choice to matter more than it did.

I hit almost the same issue last night.

[macrotinker]

Thanks, that helps. The pattern around structured output has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.

[marbletrack]

What worked for me was pretty simple. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.

[circuitwire58]

What exact setup are you running? Is this local-only or are you routing anything externally?

[routerunner]

Did a small comparison this afternoon. On 5090 with LM Studio, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.

[marbleyard32]

Did a small comparison this afternoon. On 5090 with LM Studio, I saw basically the same behavior. The surprise was that memory pressure showed up befo

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.