license: apache-2.0
language:
- en
tags:
- moe
- merge
"[We] are joined by the bonds of love. And you cannot track that, not with a thousand bloodhounds, and you cannot break it, not with a thousand swords."
This is the repo for the GGUF files
A frankenMoE not only using far better methodology and fundamental understanding of SMoE, but completely focused around intellectual roleplay. This model doesn't actually have redundancy like most MoE does...but if you encounter this, try to keep things fresh with the model by either introducing new concepts often, or through drμgs. (no not that kind)
The models that were implemented are as follows:
- mlabonne/Beagle14-7B - base
- fblgit/una-cybertron-7b-v3-OMA - expert #1
- rwitz/go-bruins-v2 - expert #2
- mlabonne/Beagle14-7B - expert #3
- mlabonne/Beagle14-7B - expert #4
Completely mogs mixtral instruct 0.1 across multiple benchmarks at half the size
Provided files
| Name | Quant method | Bits | Size | Max RAM required | Use case |
|---|---|---|---|---|---|
| Q2_K Tiny | Q2_K | 2 | 7.87 GB | 9.87 GB | smallest, significant quality loss - not recommended for most purposes |
| Q3_K_M | Q3_K_M | 3 | 10.28 GB | 12.28 GB | very small, high quality loss |
| Q4_0 | Q4_0 | 4 | 13.3 GB | 15.3 GB | legacy; small, very high quality loss - prefer using Q3_K_M |
| Q4_K_M | Q4_K_M | 4 | 13.32 GB | 15.32 GB | medium, balanced quality - recommended |
| Q5_0 | Q5_0 | 5 | 16.24 GB | 18.24 GB | legacy; large, balanced quality |
| Q5_K_M | Q5_K_M | 5 | ~16.24 GB | ~18.24 GB | large, balanced quality - recommended |
| Q6 XL | Q6_K | 6 | 19.35 GB | 21.35 GB | very large, extremely minor degradation |
| Q8 XXL | Q8_0 | 8 | 25.1 GB | 27.1 GB | very large, extremely minor degradation - not recommended |
"What is a Mixture of Experts (MoE)?"
(from the MistralAI papers...click the quoted question above to navigate to it directly.)
The scale of a model is one of the most important axes for better model quality. Given a fixed computing budget, training a larger model for fewer steps is better than training a smaller model for more steps.
Mixture of Experts enable models to be pretrained with far less compute, which means you can dramatically scale up the model or dataset size with the same compute budget as a dense model. In particular, a MoE model should achieve the same quality as its dense counterpart much faster during pretraining.
So, what exactly is a MoE? In the context of transformer models, a MoE consists of two main elements:
Sparse MoE layers are used instead of dense feed-forward network (FFN) layers. MoE layers have a certain number of “experts” (e.g. 32 in my "frankenMoE"), where each expert is a neural network. In practice, the experts are FFNs, but they can also be more complex networks or even a MoE itself, leading to hierarchical MoEs!
A gate network or router, that determines which tokens are sent to which expert. For example, in the image below, the token “More” is sent to the second expert, and the token "Parameters” is sent to the first network. As we’ll explore later, we can send a token to more than one expert. How to route a token to an expert is one of the big decisions when working with MoEs - the router is composed of learned parameters and is pretrained at the same time as the rest of the network.
At every layer, for every token, a router network chooses two of these groups (the “experts”) to process the token and combine their output additively.
Switch Layer MoE layer from the Switch Transformers paper
So, to recap, in MoEs we replace every FFN layer of the transformer model with an MoE layer, which is composed of a gate network and a certain number of experts.
Although MoEs provide benefits like efficient pretraining and faster inference compared to dense models, they also come with challenges:
Training: MoEs enable significantly more compute-efficient pretraining, but they’ve historically struggled to generalize during fine-tuning, leading to overfitting.
Inference: Although a MoE might have many parameters, only some of them are used during inference. This leads to much faster inference compared to a dense model with the same number of parameters. However, all parameters need to be loaded in RAM, so memory requirements are high. For example, [given a MoE like Mixtral 8x7B](https://huggingface.co/blog/moe), we’ll need to have enough VRAM to hold a dense 47B parameter model. Why 47B parameters and not 8 x 7B = 56B? That’s because in MoE models, only the FFN layers are treated as individual experts, and the rest of the model parameters are shared. At the same time, assuming just two experts are being used per token, the inference speed (FLOPs) is like using a 12B model (as opposed to a 14B model), because it computes 2x7B matrix multiplications, but with some layers shared (more on this soon).
If all our tokens are sent to just a few popular experts, that will make training inefficient. In a normal MoE training, the gating network converges to mostly activate the same few experts. This self-reinforces as favored experts are trained quicker and hence selected more. To mitigate this, an auxiliary loss is added to encourage giving all experts equal importance. This loss ensures that all experts receive a roughly equal number of training examples. The following sections will also explore the concept of expert capacity, which introduces a threshold of how many tokens can be processed by an expert. In transformers, the auxiliary loss is exposed via the aux_loss parameter.
"Wait...but you called this a frankenMoE?"
The difference between MoE and "frankenMoE" lies in the fact that the router layer in a model like the one on this repo is not trained simultaneously.