Platform For AI:Use public resources

Billing

Public resources are billed on pay-as-you-go basis. For more information, see Billing of Elastic Algorithm Service (EAS).

Billing start

• When you deploy a model service on public resources using specific instance types, billing starts after the service is deployed and enters the Running state.

• Platform for AI (PAI) provides a free 30 GiB system disk for each instance node in public resources. Expand the system disk on pay-as-you-go basis. Billing for the system disk starts immediately upon creation.

Billing stop

• To stop a service and its billing, go to the Elastic Algorithm Service (EAS) tab on the Inference Service page. In the Actions column for the service, click Stop.

Delete a service

Delete a service when it is no longer needed to stop billing. Before deletion, ensure the service is not actively processing requests.

Spot instances

Spot Instances allow you to deploy services in preemptible mode by setting a price ceiling, offering cost-effective compute resources.

• Benefits

  • Cost savings: Spot Instances offer low prices. Prices fluctuate in real-time based on supply and demand, typically offering significant discounts compared to standard pay-as-you-go instances on public resources.

  • Price tiers: Spot Instances are available with or without a protection period. The price tiers, from lowest to highest, are: no protection period < one-hour protection period < standard instance.

• Acquisition conditions

  • A spot Instance is acquired when there is sufficient inventory and your bid price meets or exceeds the current market price.

• Release conditions: Instance release is determined by the spot instance retention period setting.

  • One-hour protection period: Guarantees one hour of uninterrupted usage. The instance will not be released during this period but may be automatically released after the protection period ends.

  • No protection period: Continuous use is not guaranteed. The instance may be automatically released at any time due to changes in inventory or market price.

• Billing model

  • Spot Instances use a pay-as-you-go model, with charges calculated based on the real-time market price.

Multiple instance types

If you specify only a single instance type when deploying a service, deployment can fail or be delayed due to insufficient inventory of that type. To address this, EAS supports selecting multiple instance types during deployment. The system iterates through the specified instance types in the configuration to launch resources, which significantly reduces the risk of deployment failure caused by a single type being out of stock.

• Instance usage order

  When you create or update a service, specify multiple instance types, such as Spot Instances and standard instances. During deployment, the system attempts to use these instances in the order you configured them. If a Spot Instance bid fails or an instance type is out of stock, the system automatically proceeds to the next instance type in the configured list.

• Resource release and reallocation

  If a configured spot Instance is released due to changes in inventory or market price, EAS automatically reallocates the highest-priority available resource based on your configuration to ensure service continuity.

Expand system disk storage

PAI provides a free 30 GiB system disk for each instance node on public resources. If you need more capacity, additional capacity is billed based on usage. For more information about billing, see Billing of Elastic Algorithm Service (EAS).

Procedure

{
    "metadata": {
        "name": "test",
        "instance": 1,
        "workspace_id": "your-workspace-id",
        "disk": "40Gi"
    },
    "cloud": {
        "computing": {
            "instances": [
                {
                    "type": "ecs.c8i.2xlarge",
                    "spot_price_limit": 1
                },
                {
                    "type": "ecs.c8i.xlarge"
                }
            ],
            "disable_spot_protection_period": true
        }
    },
    "containers": [
        {
            "image": "eas-registry-vpc.cn-hangzhou.cr.aliyuncs.com/pai-eas/python-inference:py39-ubuntu2004",
            "script": "python app.py",
            "port": 8000
        }
    ]
}

FAQ

References

• Public resources do not guarantee resource availability. We recommend using dedicated resources to deploy services. For more information, see Use EAS resource groups.

• If you need to connect directly to your service through a VPC for high-speed access and low latency, or your EAS service needs to access other cloud products in the same VPC, see Access the Internet or internal networks from EAS.

• Configure a log service for public resources. Logs generated by EAS services deployed on public resources are stored in the log service, allowing you to monitor your EAS services in real time. For more information, see Configure Simple Log Service for a resource group.