Skip to main content
These are the baselines Fish Audio deploys against. Confirm final sizing with your account team once your traffic profile and target GPU are known: time-to-first-audio and throughput depend on the model, GPU, text length, and concurrency, and should be measured on your own hardware before you commit to a capacity plan.

Kubernetes deployments

Cluster topology

Verify the CPU and memory figures against your own chart version by rendering the release and summing the requests; they move with the default values.

GPUs

On AWS, p5.48xlarge (H100) is an acceptable baseline and p5en.48xlarge (H200) is the preferred target. Validate GPU instance quota in the target region before scheduling a deployment window.

Shared storage

Provide at least 1 TB of usable shared storage backed by EFS, NFS, or an equivalent service, mounted at the same path on every node that runs Fish Audio workloads (/mnt/share by default, configurable through global.sharedStorageHostPath). The chart mounts it into containers with hostPath volumes and creates no PersistentVolumeClaims.
The hostPath mount is created with DirectoryOrCreate. A node that is missing the shared mount silently gets a local directory instead, and the deployment looks healthy while data splits across nodes. Verify the mount on every node before installing — see the preflight checks in Kubernetes deployment.
Confirm the following with your storage team: how the mount is applied to newly added nodes, the throughput mode, the backup policy, mount target reachability, and expected growth of the model and cache data. Redis is installed by the chart and does not use shared storage. Its append-only file is backed by node-local ephemeral storage, so provision ephemeral capacity on the nodes that host it, plus headroom for rewrites.

Platform baseline

The cluster also needs working in-cluster DNS, a dedicated namespace, node labels and taints for GPU scheduling, and a Pod Security level in that namespace that permits hostPID and hostIPC, which the inference workers require.

Network

All-in-One container host

Preflight commands

Run these before you install anything.
Confirm that GPU nodes advertise allocatable GPUs:
If your policy allows a validation pod, confirm the runtime end to end:
On the All-in-One host, the equivalent check is:

Next step

Once the platform checks pass, authenticate to the Fish Audio registry in Registry access.