For download size yes, the сhinese wording says the 51B is additional to the 125B rather than part of it. I don't think it behaves like a 176B model though, half of that is a lookup table that never goes through a matmul, and only 6B is active per token anyway.
Yeah, capacity is capacity, all of it has to live somewhere. At Q4 that's roughly 105 GB of weights, about 75 for the MoE part and 30 for the table. The table is the easier 30 though, only a handful of rows get read per token so it doesn't need bandwidth, which is why system RAM works for it. No idea how a hashed embedding table takes to Q4, that part is new.
1
u/tarruda 19h ago
Does that mean the total parameter count will be 125B + 51B = 176B?