SchedulerX bills distributed job scheduling on a pay-as-you-go basis, based on the job hosting capacity and the job scheduling capacity that your applications consume. The following sections define the billing terms, compare the two editions, describe each billable item and its tiered prices, and walk through a complete billing example.
Terms
Execution mode — how a job runs. A job is either a standalone job or a non-standalone job. Non-standalone jobs include broadcast jobs, sharding jobs, MapReduce jobs, and visual MapReduce jobs.
Capacity unit (CU) — the unit in which SchedulerX measures both job hosting capacity and job scheduling capacity. All SchedulerX prices are expressed per CU.
Job hosting — the billable capacity that comes from the jobs enabled in an application. Job hosting capacity depends on the number of enabled jobs and the number of connected workers.
Job scheduling — the billable capacity that comes from running jobs. Each scheduling run consumes as many CUs as the number of workers that are scheduled for that run.
Total job hosting capacity — the sum of the job hosting CUs of all applications. This value is unrelated to the number of times that jobs are scheduled each day.
Total job scheduling capacity — the sum of the scheduling CUs of all scheduling runs of the current day. Unlike job hosting capacity, this value grows with the scheduling frequency of your jobs.
Edition comparison
SchedulerX provides two editions: Basic Edition and Professional Edition. The following table describes the features that each edition supports.
indicates that a feature is supported, and 
indicates that a feature is not supported.
| Feature | Basic Edition | Professional Edition |
| Basic scheduling capabilities | | |
| Logging service | | |
| Stack trace viewing | | |
| Tracing | | |
| User dashboard | | |
| Workflow instance diagram | | |
| Link encryption | | |
| Tag-based routing policy | | |
| Visual MapReduce (parallel computing) | A maximum of 300 subtasks. Search is not supported. | A maximum of 1,000 subtasks. Custom tags and search are supported. |
| Maximum number of historical job records | Displays the 30 most recent execution records of a job. | Displays the 300 most recent execution records of a job and supports viewing archived execution records of the previous 60 days. |
| Alert methods | DingTalk, email | DingTalk, email, text message, phone call, WeCom, Lark |
| Maximum number of jobs per application | 1,000 | 100,000 |
| OpenAPI | Supports only the API operations for creating, updating, and deleting jobs. | Supports all API operations. |
| Billable items | Job hosting CUs | Job hosting CUs and job scheduling CUs |
The following details apply to specific rows in the preceding table:
Logging service — The SchedulerX logging service is not a separate billable item. Each job is throttled to 5 log entries per second.
Maximum number of jobs per application — To increase the quota of Professional Edition, contact technical support.
Basic Edition covers basic scheduling capabilities and is billed on job hosting CUs only. Choose Professional Edition if you need capabilities such as the logging service, tracing, the user dashboard, extended alert methods, or full OpenAPI access. Professional Edition also adds job scheduling CUs as a billable item. Because those CUs accumulate with every scheduling run, high-frequency jobs widen the cost difference between the two editions.
Billing methods
Pay-as-you-go
SchedulerX instances are billed on a pay-as-you-go basis. You are charged for the capacity that your applications consume, and the fee for each billable item is calculated from its tiered unit prices.
Billable items
SchedulerX has two billable items: job hosting CUs and job scheduling CUs. Basic Edition is billed based on job hosting CUs. Professional Edition is billed based on the sum of job hosting CUs and job scheduling CUs.
Job hosting CUs
Fees are calculated based on the total number of job hosting CUs. The job hosting CUs of a single SchedulerX application are calculated as follows:
Job hosting CUs of a single SchedulerX application = Number of enabled standalone jobs + Number of enabled non-standalone jobs × Number of workers connected to the application
The following billing examples are for reference only. The actual fees are subject to the console page (or buy page) of the cloud service that you purchase.
For example, you have two SchedulerX applications: A and B.
Application A is connected to 10 client workers and has 8 standalone jobs and 2 non-standalone jobs enabled.
Application B is connected to 5 client workers and has 2 standalone jobs and 3 non-standalone jobs enabled.
Your total job hosting capacity per day is calculated as follows:
Total job hosting capacity = (8 + 2 × 10) + (2 + 3 × 5) = 45 CUs/day
The number of enabled jobs is counted only as the maximum number of jobs that are enabled on the current day. For example, if you create 1,000 jobs and delete 1,000 jobs on the current day and a maximum of 100 jobs are enabled at the same time, only 100 jobs are counted.
Job scheduling CUs
The total number of job scheduling CUs equals the sum of the scheduling CUs of all scheduling runs of the current day. The scheduling CUs of a single scheduling run equal the number of workers that are scheduled for that run:
Standalone job — one scheduling CU per scheduling run.
Non-standalone job — one scheduling CU for each worker that is scheduled for the run.
Second-level job — the counting rule depends on the time type:
second_delay: one scheduling CU is counted per minute for the job, regardless of the configured run interval and the number of workers.cronorfixed_rate: scheduling CUs are counted for each scheduling run based on the scheduling frequency.
For example, SchedulerX application A is connected to 2 client workers and has the following jobs enabled: 5 standalone jobs that each run once a day, 3 sharding jobs that each run every 30 minutes, and 2 second-level jobs (time type: second_delay) that each run every 10 seconds. The job scheduling CUs of application A per day (24 hours) are calculated as follows:
Standalone jobs: 5 jobs × 1 scheduling run per day = 5 CUs/day
Sharding jobs: 3 jobs × 2 workers × 2 scheduling runs per hour × 24 hours = 288 CUs/day
Second-level jobs: 2 jobs × 60 CUs per hour (one CU per minute) × 24 hours = 2,880 CUs/day
Total job scheduling capacity of application A = 5 + 288 + 2,880 = 3,173 CUs/day
Pricing
Both billable items are priced in tiers, and the tiers apply progressively. The capacity that falls within a tier is charged at the unit price of that tier, and the fees of all tiers are added up to obtain the fee for the billable item.
The notation [a, b] indicates a value range that includes both a and b, and the notation (a, b] indicates a value range that excludes a and includes b. The actual prices are subject to the buy page.
The following table lists the tiered unit prices of job hosting CUs.
| Billing tier | Total job hosting capacity (CUs) | Unit price (USD/CU/day) |
| Tier 1 | [0, 5] | Free |
| Tier 2 | (5, 200] | 0.02 |
| Tier 3 | (200, 1,000] | 0.01 |
| Tier 4 | (1,000, 10,000] | 0.005 |
| Tier 5 | More than 10,000 | 0.002 |
The following table lists the tiered unit prices of job scheduling CUs.
| Billing tier | Cumulative job scheduling CUs per day | Unit price (USD/CU) |
| Tier 1 | [0, 30] | Free |
| Tier 2 | (30, 10,000] | 0.002 |
| Tier 3 | (10,000, 50,000] | 0.001 |
| Tier 4 | (50,000, 100,000] | 0.0005 |
| Tier 5 | (100,000, 1,000,000] | 0.0002 |
| Tier 6 | More than 1,000,000 | 0.0001 |
Billing examples
Assume that you purchase SchedulerX Professional Edition and have two SchedulerX applications: A and B.
Application A is connected to 5 client workers and has 100 standalone jobs and 10 non-standalone jobs enabled.
Application B is connected to 2 client workers and has 50 standalone jobs and 2 non-standalone jobs enabled.
The standalone jobs and non-standalone jobs that are enabled in applications A and B are each scheduled 50 times per day, and one month is 30 days.
The capacity of both billable items is calculated as follows:
Total job hosting capacity = job hosting CUs of application A (100 + 10 × 5) + job hosting CUs of application B (50 + 2 × 2) = 204 CUs/day
Total job scheduling capacity = job scheduling CUs of application A (100 × 1 × 50 + 10 × 5 × 50) + job scheduling CUs of application B (50 × 1 × 50 + 2 × 2 × 50) = 10,200 CUs/day
The job hosting CU fees are calculated as follows:
Tier 1 fee: 5 × 0 = USD 0
Tier 2 fee: (200 - 5) × 0.02 = USD 3.9
Tier 3 fee: (204 - 200) × 0.01 = USD 0.04
Job hosting CU fee (pay-as-you-go) = 0 + 3.9 + 0.04 = USD 3.94/day
The job scheduling CU fees are calculated as follows:
Tier 1 fee: 30 × 0 = USD 0
Tier 2 fee: (10,000 - 30) × 0.002 = USD 19.94
Tier 3 fee: (10,200 - 10,000) × 0.001 = USD 0.2
Job scheduling CU fee (pay-as-you-go) = 0 + 19.94 + 0.2 = USD 20.14/day
Monthly job hosting CU fee = 3.94 × 30 = USD 118.2/month
Monthly job scheduling CU fee = 20.14 × 30 = USD 604.2/month
Total daily fee of SchedulerX applications A and B = job hosting CU fee + job scheduling CU fee = 3.94 + 20.14 = USD 24.08/day
Total monthly fee of SchedulerX applications A and B = 118.2 + 604.2 = USD 722.4/month
References
If you no longer need a distributed job scheduling instance that you purchased, you can unsubscribe from the instance resources to avoid additional fees. For more information, see Unsubscribe from resources.