embedding drift issues: worth it?

[torchstation]

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 router policy.

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.

If I had to summarize the lesson so far, it would be that clean setup and observability beat clever guesses.

[tensorfield88]

This keeps coming up in conversation so I figured I'd start a thread.

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly.

[labline]

Tried to reproduce it just now. 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.

[homelabhenry]

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.

[batchpeak]

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

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

[mangofield33]

[quote]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 obviou

I don't think that's the whole story. I get why that seems right, but on GB200 the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.

[localpatch78]

Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.

[macrolab]

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.

I'm happy to test one more variant if you want a second data point.

[oxideworks59]

Thanks, that helps. That matches what I saw on 5090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. The logs were somehow calmer than I was.

[macronest]

I don't think that's the whole story. I get why that seems right, but on mini PC the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.