3 ms·
I’d say that this expands on MoE really - MoE chooses dynamically which groups of weights may be needed, but it’s whole matrixes. Here it’s ingle weights. Also
by kolinko 3y ago
I’d say that this expands on MoE really - MoE chooses
dynamically which groups of weights may be needed, but it’s whole matrixes. Here it’s ingle weights.
Also, this works on top of MoE beautifully - most of the development and testing was done on Mixtral and it was getting (anecdotally) even better results - getting down to 15-18% effort before seriously losing quality.
I decided to release the Mistral version, but Mixtral was fully operational a few commits back :)
Also, the cool thing - because you can load only the top say 70% weights, I was running Mixtral full precision on my MB 96G - there were no bemchmarks for this in other impls because others need to load full model into the memory.
The real question is Q8 performance - I didn’t implement it fully so far.
- anentropic 3y agoCould you add a git tag for the last commit where Mixtral was working?
- kolinko 3y agoI think it was somewhere around that tag: https://github.com/kolinko/effort/releases/tag/5.0-last-mixtral-working https://github.com/kolinko/effort/releases/tag/5.0-last-mixt... Cannot rerun easily any more, because the underlying model/weight names changed in the meantime. It doesn't help that Mixtral's published .safetensor files seem messed up, and I needed to hack a conversion from pytorch - it added an extra layer of confusion into the project.