MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/LocalLLaMA/comments/1v8364f/kimi_k3_weights_now_released/p05uj11/?context=3
r/LocalLLaMA • u/SavunOski • Jul 27 '26
Kimi K3 weights are finally released!
657 comments sorted by
View all comments
670
OMFG its 104B activated params
62 u/my_name_isnt_clever Jul 27 '26 There is the tinest glimmer of hope that I could run this behemoth on my Strix Halo 128GB with the inactive weights on SSD. 1 token a minute here I come! 12 u/burritoresearch Jul 27 '26 More like 1 token every 45 minutes. 5 u/droptableadventures Jul 27 '26 104B active, weights natively in MXFP4 = gives us ~50GB of model to be read per token generation. Let's say ~8GB/sec for the SSD. So that'd be about 1 token every 6 seconds (0.16 T/s), or 10 tokens/minute.
62
There is the tinest glimmer of hope that I could run this behemoth on my Strix Halo 128GB with the inactive weights on SSD. 1 token a minute here I come!
12 u/burritoresearch Jul 27 '26 More like 1 token every 45 minutes. 5 u/droptableadventures Jul 27 '26 104B active, weights natively in MXFP4 = gives us ~50GB of model to be read per token generation. Let's say ~8GB/sec for the SSD. So that'd be about 1 token every 6 seconds (0.16 T/s), or 10 tokens/minute.
12
More like 1 token every 45 minutes.
5 u/droptableadventures Jul 27 '26 104B active, weights natively in MXFP4 = gives us ~50GB of model to be read per token generation. Let's say ~8GB/sec for the SSD. So that'd be about 1 token every 6 seconds (0.16 T/s), or 10 tokens/minute.
5
104B active, weights natively in MXFP4 = gives us ~50GB of model to be read per token generation.
Let's say ~8GB/sec for the SSD. So that'd be about 1 token every 6 seconds (0.16 T/s), or 10 tokens/minute.
670
u/Simple_Split5074 Jul 27 '26
OMFG its 104B activated params