What GPU do I need to run Alimzhan/wav2vec2-large-xls-r-300m-albanian-colab?
315M parameters, published in F32. View on Hugging Face
Set up wav2vec2-la…m-albanian-colabwav2vec2-large-xls-r-300m-albanian-colab is published by Alimzhan on Hugging Face, with 214,120 downloads and 1 like to date. It's a Wav2Vec2ForCTC model built for automatic-speech-recognition, published natively in F32.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision, plus a fixed overhead for activations and allocator fragmentation. Speech models don't build the same growing KV-cache a text model does. Memory scales primarily with input audio length. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP32 | 1.2 GB | 1.4 GB | V100 | 1 | $0.088/hr |
| FP8 (quantized) | 0.3 GB | 0.4 GB | RTX 5060 Ti | 1 | $0.110/hr |
| INT4 (quantized) | 0.1 GB | 0.2 GB | RTX 5060 Ti | 1 | $0.110/hr |
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run wav2vec2-large-xls-r-300m-albanian-colab at its published (F32) precision: 1× V100, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
wav2vec2-large-xls-r-300m-albanian-colab: common questions
How much VRAM does wav2vec2-large-xls-r-300m-albanian-colab need?
1.4 GB at FP32, 0.4 GB at FP8 (quantized), 0.2 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 1.2 GB of weights plus inference overhead is the whole requirement.
Can wav2vec2-large-xls-r-300m-albanian-colab run in 16-bit instead of FP32?
Yes. Its published weights are FP32, 1.2 GB, or 1.4 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 0.6 GB, or 0.7 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.
How many copies of wav2vec2-large-xls-r-300m-albanian-colab fit on one V100?
11, by VRAM alone. That card carries 16.0 GB and one copy needs 1.4 GB at FP32, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 11 copies is not 11 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More Wav2Vec 2.0 models
- wav2vec2-xls-r-300m-ftspeech (315M, F32)
- nb-wav2vec2-300m-bokmaal-v2 (315M, F32)
- wav2vec2-large-xlsr-53-english (315M, F32)
- romanian-wav2vec2 (315M, F32)
- wav2vec2-xls-r-300m-hebrew (315M, F32)
Related reading: V100 pricing and specs, and The best GPUs for AI, ranked.
