What GPU do I need to run ai4bharat/indic-parler-tts?
938M parameters, published in F32. View on Hugging FaceGated
Set up indic-parler-ttsindic-parler-tts is published by ai4bharat on Hugging Face, with 355,610 downloads and 313 likes to date. It's a ParlerTTSForConditionalGeneration model built for text-to-speech, published natively in F32, and gated: you'll need to accept the model's terms on Hugging Face before downloading weights.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision, plus a fixed overhead for KV-cache, activations, and fragmentation. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP32 | 3.5 GB | 4.2 GB | V100 | 1 | $0.088/hr |
| FP8 (quantized) | 0.9 GB | 1.0 GB | RTX 4070 Super | 1 | $0.121/hr |
| INT4 (quantized) | 0.4 GB | 0.5 GB | RTX 4070 Super | 1 | $0.121/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 indic-parler-tts 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.
indic-parler-tts: common questions
How much VRAM does indic-parler-tts need?
4.2 GB at FP32, 1.0 GB at FP8 (quantized), 0.5 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 3.5 GB of weights plus inference overhead is the whole requirement.
Do I need approval to download indic-parler-tts?
Yes. ai4bharat gates this repository on Hugging Face, so you have to accept its terms with a signed-in account before the weights will download. It does not change the 4.2 GB the model needs once you have them.
Can indic-parler-tts run in 16-bit instead of FP32?
Yes. Its published weights are FP32, 3.5 GB, or 4.2 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 1.7 GB, or 2.1 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.
How many copies of indic-parler-tts fit on one V100?
3, by VRAM alone. That card carries 16.0 GB and one copy needs 4.2 GB at FP32, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 3 copies is not 3 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More Parler-TTS models
- parler-tts-mini-multilingual-v1.1 (938M, F32)
- parler-tts-mini-v1 (878M, F32)
- parler-tts-large-v1 (2.3B, F32)
Related reading: V100 pricing and specs, and The best GPUs for AI, ranked.
