Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
reranking still worth it for small sets
#1
Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on A6000, or squeeze more out of the stack and deal with the complexity.

Interested in tradeoffs more than fan loyalty.
Reply
#2
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#3
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Apple Silicon • MLX mostly
Reply
#4
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal.
watching release notes so you don't have to
Reply
#5
Appreciate the detail. I don't think your conclusion is far off.
M3 Max • MLX • local-first
Reply
#6
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals. Once you know the plain path works, then add the faster path back in piece by piece.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)