Zai Org · GLM Z1

GLM-Z1-32B-0414

Unverified · community-discovered, not yet reviewed

GLM-Z1-32B-0414 is a discovered model from public model catalogues. Badgr builds a GPU serving profile from source metadata, estimated VRAM, context length, and available execution routes.

Last validated or meaningfully updated: Dynamic source discovery

ChatMultilingualFine-tunable

Availability

Not yet Badgr AI API

Not currently validated

Dedicated endpoint

Available through Badgr

Custom GPU deployment

Available through Badgr

Deployment profile

Architecture
Source metadata pending
Minimum VRAM
~68GB
Context
Source dependent

Recommended: A100 80GB. VRAM is an estimate and increases with context, cache, concurrency, and runtime overhead.

Model identity

Languages
zh, en
Updated
1 years ago
HuggingFace revision
8eb2858992

Popularity and trust

Downloads (last month)

45.7K

Likes

196

Spaces using this model

3

Files and formats

Weight formats

Safetensors

Repository files

24

Chat template

Available

GPU deployment scenarios

Estimated from parameter count and quantisation. Will switch to “Verified by Badgr” once a real run backs a tier.

Testing

A100 80GB

Short context, low concurrency

Small production

H100 80GB

8K context, 1-4 concurrent requests

Higher throughput

H200 141GB

32K context, continuous batching

Large production

A100 80GB

Higher concurrency

Estimated — multimodal inputs, long context, and concurrency all increase real VRAM use beyond this estimate.

Also runs well on H100 80GB, H200 141GB. Available in United States, Europe, Asia Pacific.

Serving compatibility

RuntimeStatusNotes
vLLMEstimatedUsed for Badgr dedicated endpoints
TransformersDeclared by sourceBasic fallback
llama.cppRequires GGUF conversionNo GGUF weights found in repo
SGLangUnknownNot evaluated
TensorRT-LLMUnknownConversion may be required
TGIUnknownNot evaluated

Ready-to-run Badgr configurations

Quick test

badgr serve zai-org/GLM-Z1-32B-0414 --max-cost 2

Dedicated endpoint command

badgr serve zai-org/GLM-Z1-32B-0414 --gpu A100 80GB --max-cost 10

Advanced configuration (defaults to automatic)

  • Runtime
  • Quantisation
  • GPU and GPU count
  • Context length
  • Maximum concurrency
  • Region
  • Maximum hourly spend
  • Persistent or capped runtime

Estimated pricing

Provider estimate: cold start

3–8 min

Provider estimate: endpoint cost

$1.30 – $1.40/hr

Idle cost

$0 when stopped

Per-token throughput cost is not shown here: Badgr has not benchmarked this model yet, and this page does not display figures it cannot back with real data.

Recommended Badgr routes

A100 80GB · United States

Available

from $1.30/hr

40GB VRAM/GPU

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: just now

A100 80GB · United States

Available

from $1.40/hr

40GB VRAM/GPU28 vCPU120GB RAM100GB storage

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: just now

A100 80GB · United States

Available

from $1.40/hr

2x GPU40GB VRAM/GPUSame host60 vCPU240GB RAM100GB storage

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: Good

Last checked: just now

A100 80GB · United States

Available

from $1.40/hr

4x GPU40GB VRAM/GPUSame host124 vCPU480GB RAM100GB storage

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: just now

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: Good

Last checked: Live marketplace price not available yet

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: Live marketplace price not available yet

Known limitations

  • Source-discovered pages use best-effort metadata from an automated publication gate, not manual review.
  • Licence, gated access, runner compatibility, and exact memory use should be checked before production deployment.

Related troubleshooting