This topic describes the comparison, billing methods, billable items, pricing, and billing examples of SchedulerX.
Basic concepts
Execution mode: specifies how jobs are run. Based on the execution mode, jobs are classified into standalone jobs and non-standalone jobs. Non-standalone jobs are further classified into broadcast jobs, sharding jobs, MapReduce jobs, and visual MapReduce jobs.
Total job scheduling capacity: the total amount of distributed job scheduling capacity that is configured and enabled by using SchedulerX. Unit: capacity unit (CU).
Total job hosting capacity: the total amount of job hosting capacity across all applications, which is irrelevant to the number of times the job scheduling jobs run per day.
Edition comparison
SchedulerX provides Basic Edition and Professional Edition. The following table describes the features supported by the two editions.
In the following table,
indicates that the feature is supported and
indicates that the feature is not supported.
Feature | Basic Edition | Professional Edition |
Basic scheduling capability |
|
|
Logging |
|
Note The logging feature of SchedulerX is not billed separately. |
Stack display |
|
|
Tracing |
|
|
User dashboard |
|
|
Workflow instance diagram |
|
|
Data encryption during data transfer |
|
|
Tag-based routing policy |
|
|
Visual MapReduce (parallel computing) | Supports up to 300 tasks but does not support task searching. | Supports up to 1,000 tasks, custom tags, and task searching. |
Maximum number of historical jobs displayed | Displays the last 30 jobs. | Displays the last 300 jobs. |
Alert notification method | DingTalk and email. | DingTalk, email, text message, mobile phone, WeCom, and Lark. |
Maximum number of jobs per application | 1,000 | 100,000. To gain technical support for scale-out, join the DingTalk group (ID: 23103656). |
API | Supports API operations that are used to create, update, or delete jobs. | Supports all API operations. |
Billable item | Job hosting CUs. | Job hosting CUs and job scheduling CUs. |
Billing methods
Pay-as-you-go
Basic Edition: You are billed based on the number of job hosting CUs.
Professional Edition: You are billed based on the total number of job hosting CUs and job scheduling CUs.
Billable items
SchedulerX billable items are job hosting CUs and job scheduling CUs. If you use Basic Edition, you are billed based on the number of job hosting CUs. If you use Professional Edition, you are billed based on the total number of job hosting CUs and job scheduling CUs.
Job hosting CUs
The job hosting fee charged for a SchedulerX application is calculated based on the number of job hosting CUs consumed by the application. The following formula shows how to calculate the number of job hosting CUs consumed by an application:
Number of job hosting CUs of a SchedulerX application = Number of enabled standalone jobs + Number of enabled non-standalone jobs × Number of workers connected to the application
The following example is provided for reference only. Go to the service console or buy page to view the actual price.
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.
In this case, the total number of job hosting CUs consumed per day is calculated by using the following formula:
Total number of job hosting CUs = (8 + 2 × 10) + (2 + 3 × 5) = 45
The maximum number of jobs running at the same time on a day is counted as the number of enabled jobs of the day. For example, if 1,000 jobs are created and 1,000 jobs are deleted on a day, but only a maximum of 100 jobs run at the same time, the number of enabled jobs of the day is counted as 100.
Job scheduling CUs
The total number of job scheduling CUs is equal to the total number of all job scheduling CUs on the current day. The number of job scheduling CUs for a single job is equal to the number of workers scheduled each time. For example:
For a standalone job, one job scheduling CU is consumed.
For a non-standalone job, the number of job scheduling CUs consumed at a time is equal to the number of workers scheduled for the job.
Second-level jobs:
If the time type is set to second_delay, only one job scheduling CU is counted every minute.
If the time type is set to cron or fixed_rate, the number of job scheduling CUs consumed each time is calculated based on the scheduling frequency.
For example, SchedulerX Application A connected to two client workers, five standalone jobs are enabled, each standalone job runs once a day, three sharding jobs run every half hour, and two second-level jobs with the time type set to second_delay run every 10 seconds. The number of job scheduling CUs consumed every day (24 hours) for Application A is calculated by using the following formulas:
Number of standalone job scheduling CUs = 5 standalone jobs × 1 scheduling per day = 5 CUs per day
Number of sharding job scheduling CUs = 3 sharding jobs × 2 workers for each job × 2 scheduling times per day (24 hours) = 288 CUs per day
Number of second-level job scheduling CUs = 2 second-level jobs × 60 scheduling times per day (24 hours) = 2,880 CUs per day
Total number of job scheduling CUs consumed for Application A = 5 + 288 + 2880 = 3173 CUs per day
Pricing
(a,b] is used to indicate the quantity range, within which a is excluded and b is included. You can view the actual price on the buy page.
Job hosting CUs (pay-as-you-go)
If you use Basic Edition, you are charged for the number of job hosting CUs that are consumed. The following table describes the billing tiers.
Billing tier | Total number of job hosting CUs | Unit price (USD per CU-day) |
First tier | 0-5 | Free |
Second tier | 6-200 | 0.02 |
Third tier | 201-1,000 | 0.01 |
Fourth tier | 1,001-10,000 | 0.005 |
Fifth tier | N (N > 10,000) | 0.002 |
Job scheduling CUs (pay-as-you-go)
If you use Professional Edition, you are charged for the number of job scheduling CUs that are consumed. The following table describes the billing tiers.
Billing tier | Total number of job scheduling CUs per day | Unit price (USD per CU) |
First tier | [0,30] | Free |
Second tier | (30, 10,000] | 0.002 |
Third tier | (10,000, 50,000] | 0.001 |
Fourth tier | (50,000, 100,000] | 0.0005 |
Fifth tier | (100,000, 1,000,000] | 0.0002 |
Sixth tier | More than 1,000,000 | 0.0001 |
Billing example
In this example, you have purchased 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 and non-standalone jobs enabled by Application A and Application B are scheduled 50 times per day for 30 days.
Total number of job hosting CUs consumed per day = Number of job hosting CUs consumed for Application A (100 + 10 × 5) + Number of job hosting CUs consumed for Application B (50 + 2 × 2) = 204
You can calculate the fees for job hosting CUs based on the fees of different tiers.
First-tier fee: 5 × 0 = USD 0
Second-tier fee: (200 - 5) × 0.02 = USD 3.9
Third-tier fee: (204 - 200) × 0.01 = USD 0.04
Fee for job hosting CUs (pay-as-you-go) per day = 0 + 3.9 + 0.04 = USD 3.94
Total number of job scheduling CUs per day = Number of job scheduling CUs consumed for Application A (100 × 1 × 50 + 10 × 5 × 50) + Number of job scheduling CUs consumed for Application B (50 × 1 × 50 + 2 × 2 × 50) = 10200
You can calculate the fees for job scheduling CUs based on the fees of different tiers.
First-tier fee: 30 × 0 = USD 0
Second-tier fee: (10000 - 30) × 0.002 = USD 19.94
Third-tier fee: (10,200 - 10,000) × 0.001 = USD 0.2
Fee for job scheduling CUs (pay-as-you-go) per day = 0 + 19.94 + 0.2 = USD 20.14
Monthly fee for job hosting CUs = 3.94 × 30 = USD 118.2
Monthly fee for job scheduling CUs = 20.14 × 30 = USD 604.2
Total fees for SchedulerX applications A and B per month = 118.2 + 604.2 = USD 722.4
References
If you no longer use SchedulerX instances, you can unsubscribe from these instances to prevent unexpected charges. For more information, see Refund policy.