4 ms·
One parameter is 16 bits == 2 bytes. So a model with 7 billion parameters needs 14GB of RAM for the un-quantized model, plus some overhead for the KV cache and
by sp332 3y ago
One parameter is 16 bits == 2 bytes. So a model with 7 billion parameters needs 14GB of RAM for the un-quantized model, plus some overhead for the KV cache and other "working memory" stuff but that should be fairly low for a 7B model. I expect it will work on a 16GB GPU just fine.
Quantized ones are also easy. 8 bits == 1 byte so that's 7GB for the model. 4-bit gets you below 4GB.
- semi-extrinsic 3y agoFrom the Mistral docs, it seems they need 24GB which is kind of odd? https://docs.mistral.ai/llm/mistral-v0.1 https://docs.mistral.ai/llm/mistral-v0.1
- sp332 3y agoInteresting, and that requirement is repeated on the cloud deployment pages, even the unfinished ones where that is the only requirement listed so far. https://docs.mistral.ai/category/cloud-deployment https://docs.mistral.ai/category/cloud-deployment I wonder if that sliding context window really blows up the RAM usage or something.
- sebzim4500 3y agoUnless I've misunderstood something, the sliding context window should decrease memory usage at inference compared to normal flash attention.
- lerela 3y agoWe have clarified the documentation, sorry about the confusion! 16GB should be enough but it requires some vLLM cache tweaking that we still need to work on, so we put 24GB to be safe. Other deployment methods and quantized versions can definitely fit on 16GB!
- brucethemoose2 3y agoShouldn't it be much less than 16GB with vLLM's 4-bit AWQ? Probably consumer GPU-ish depending on the batch size?
- brucethemoose2 3y agoIts not so straightforward, as theres some overhead aside from the weights, especially with 7B at ~4 bit. But this is probably capable of squeezing onto a 6GB (or less?) GPU with the right backend.