What GPU do I need to run google/timesfm-3.0-pytorch?

331M parameters, published in F32. View on Hugging Face

Set up timesfm-3.0-pytorch
331M
Parameters
F32
Native precision
Unknown
Architecture
time-series-forecasting
Pipeline

timesfm-3.0-pytorch is published by google on Hugging Face, with 0 downloads and 255 likes to date. It's a unlisted-architecture model built for time-series-forecasting, published natively in F32.

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
1.2 GB
1.5 GB
P4 (akash)
1
$0.032/hr
FP8 (quantized)
0.3 GB
0.4 GB
RTX 4080 (akash)
1
$0.158/hr
INT4 (quantized)
0.2 GB
0.2 GB
RTX 3070 (simplepod)
1
$0.050/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 timesfm-3.0-pytorch at its published (F32) precision: 1× P4 on akash, at $0.032/hr per GPU ($0.032/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More google models

Ready when you are

Your next GPU already
has your environment on it.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.