Volcengine Kubernetes Engine
Parameter | Description |
Parameter | Description |
works_per_node | works_per_node indicates the number of workers per node in the resource pool. nnodes indicates the total number of cluster nodes. The values must meet the following condition: works_per_node × nnodes = gpu_num.
|
nnodes | |
use_gpu | Whether to use GPU resources. Valid values:
|
max_colocate_count | The maximum number of workers. If the model requires three loaders: DiT, CLIP, and VAE, max_colocate_count needs to be set to 3. |
pool_num | The name of the resource pool. |
Parameter | Description |
Parameter | Description |
ulysess_degree | The Ulysses parallelism degree. The value needs to be divisible by head_num of the model. For example, if head_num of the Wan2.1-14B model is 40, ulysess_degree can be set to 40, 80, or another value that is divisible by 40. |
ring_degree | The Ring Attention parallelism degree. |
cfg_degree | The Classifier-Free Guidance (CFG) parallelism degree. Maximum value: 2. The Wan and HiDream models are supported. The values must meet the following condition: ulysess_degree x ring_degree x cfg_degree = gpu_num. |
base_precision | Base computation precision during model inference:
|
quantization | Quantization configuration of the model. To obtain FP8 activation quantization, select the xxx_fast mode. |
load_device | Model storage location:
|
attention_mode | Attention operator type. It is recommended to use sageattn in this scenario. This type indicates Sage Attention. Sage Attention significantly reduces VRAM usage through 8-bit quantization technology while maintaining performance. Sage Attention is suitable for devices with limited VRAM resources. |
rms_norm_function | RMS Normalization (RMSNorm) implementation:
|
Parameter | Description |
Parameter | Description |
steps | The number of sampling steps, which is the number of denoising iterations. More steps achieve higher generation quality but take longer. |
cfg | The guidance strength of the prompt. A higher value exerts a stronger influence on the generated result, but excessively high values may cause image distortion. |
shift | A node extension parameter that controls the offset during the sampling process. |
seed | The seed value, which is a random number generated during denoising. When the seed value and other parameter configurations are consistent, the generated image is reproducible. Different seed values achieve different random results. |
control after generate | Controls the behavior of the seed after it is generated. Valid values:
|
force_offload | Whether to forcibly offload model components to devices such as CPU temporarily after sampling:
|
scheduler | The noise scheduling policy, which controls the pace of noise variation during sampling. This parameter affects generation quality and efficiency. |
riflex_freq_index | Frequency channel index targeted by the RIFLEX module. A value of 0 disables the module. The default value is 6, which enables new frame generation without looping. |
denoise_strength | The level of denoising applied to the initial noise. A value of 1.0 indicates complete denoising. A lower value indicates higher randomness of the generated image. The value range is 0 to 1.0. A value of 1.0 means complete denoising, generating entirely new content based on the initial latent variables. Values less than 1.0 mean modifying the original content. |
batched_cfg | Whether to calculate CFG (Classifier-Free Guidance) in batch mode:
|
rope_function | Rotary Position Embedding (RoPE) implementation logic:
|
start_step | The starting step for sampling. 0 means full sampling. Otherwise, sampling starts from the specified step. |
end_step | The ending step for sampling. -1 indicates full sampling. Otherwise, sampling stops at the specified step. |
add_noise_to_samples | The sample noise addition switch for specifying whether to add initial noise to video samples before sampling:
|
Cloud service | Required | Preparation | Reference |
Cloud service | Required | Preparation | Reference |
GPU Cloud Computing | Yes | Provides GPU computing resources. For the video generation scenario described in this topic, it is recommended to use the following GPU Cloud Computing instance types:
tip [Beta] The preceding GPU Cloud Computing instance types are in beta. Contact your account manager of Volcano Engine to apply for a beta trial. | |
TOS | Recommended | Achieves persistent storage for the ComfyUI application. tip TOS storage can be mounted to containers only via FSX. If you use existing managed VKE clusters for heterogeneous computing, make sure that csi-fsx and fsx-service add-ons are installed in the clusters. These add-ons are automatically installed in newly created managed clusters for heterogeneous computing. | |
IAM | Required when TOS is used | Obtains the API access keys (AK and SK) of IAM to access TOS through VKE. | |
VKE | Yes | Provides managed clusters for heterogeneous computing for deploying the ComfyUI application. | |
APIG | Optional | Achieves Layer 7 routing through APIG instances. These instances are required in session persistence scenarios. warning
| |
Internet express | Recommended | Add-on installation requires content pulled from GitHub and HuggingFace, and the Internet Express service. warning
| None |
Parameter | Description |
Parameter | Description |
Select framework and orchestration | |
Deployment method | Select Predefined template deployment. |
Model | Select Wan2.1 and Infinite Talk. |
Application configuration | |
ComfyUI configuration | We recommend selecting Permanent storage for Storage location. You can configure other parameters according to your application. ServingKit will create the commonly used directories of ComfyUI in the corresponding paths, including the custom_nodes, input, output, models, and user directories. |
Instance configuration | |
Instance specification | Set Number of GPU cards to 8 and set other parameters as needed. |
More configuration |
warning
|
Service configuration | |
API Gateway | Enable API Gateway and associate the prepared APIG instance. warning Make sure that the selected APIG instance and the cluster where the application is deployed are located in the same VPC. |