i rebuilt my deepseek v4.1 flash weights on the 1017 update, v1.2 is live on 2x dgx sparks 🐋
> structured output: 141.3 tok/s
> code: 100.7 tok/s
> prose: 59.2 tok/s
and the quality held, my 2.70 bit weights scored against native 1017 on my own kl panel, the one other 1017 packs now report on
> kld 0.0243 from native 1017
> 20% closer than libertaidai's 2.9 bit pack
> top-1 agreement 95.47%
> humaneval+, mbpp+, ifeval within noise
> ifeval replies: theirs wins, 0.1135 vs 0.1199
deepseek shipped 1017 as a minor update, so i diffed it against the checkpoint my build came from, the config, tokenizer and tensor layout match byte for byte and every shard's content is new, in the slices i sampled about 27% of the 4 bit expert codes flipped and the built-in drafter moved the most
there was nothing to patch, so i pulled the 510 gb checkpoint again, measured all 15,360 experts, ran a 16 hour encode with one spark down for almost 3 hours while the other carried on solo, then dense layers, head, drafter and every eval, about 25 hours from download to serving
it runs about as fast as my launch build, which did 103.0 tok/s on code and 58.0 on prose, a verify round on code still takes 42.8 ms on both, the new weights just let the drafter land 4.31 tokens a round on that reply instead of 4.41
by the time mine finished, henryous and 0xsero had shipped 1017 packs built on my recipe, and henryous reports 0.0201 at 2.75 bits with heavier dense layers and head, closer to native than mine
so i tried that mix on my own experts, dense at 5 bits and the head at 6 got me to 0.0219 for about 5% of my speed, i'm shipping the fast build and the heavier numbers are in the repo
same engine as v1.1, so you keep the image and swap in the 1017 weights plus deepseek's 1017 engram shards
next i'm training my own drafter for it to push more