logoalt Hacker News

walrus01today at 9:34 PM1 replyview on HN

Now imagine the token/s rate decline after context fill at 200,000+ context.


Replies

Argonautlabstoday at 9:45 PM

Fair, and we didn't measure it.

Decode was flat from 128 to 512 generated tokens (0.926 → 0.923 tok/s drafter-off), but that's a 6-token prompt plus the output — total context under a thousand.

The current configuration admits about 4.4k tokens of context at all, and at anything like 200k the killer wouldn't be decode, it would be prefill: today it reads each layer's experts once per 64-row pass,

so 200k tokens of prompt would be measured in days, not minutes, until the scheduling fix.

show 1 reply