Scheduling
When to deploy your project
One of the most prominent features of the Polkadot Network is its ability to schedule different tasks on Polkadot’s Cloud. Polkadot Native Rollups are one of these tasks. Similar to other well-known cloud services, Polkadot Cloud allows projects to schedule and use its cores based on the project’s needs. If the project is expecting a high load, it can secure multiple cores to elastically scale. Conversely, during periods of low load, the project can share a core with other projects, reducing costs. This flexibility is adjustable on a cycle-by-cycle basis.
The PDP makes interacting with Polkadot’s agile coretime scheduling intuitive and user-friendly.
Schedule Right Now
The PDP constantly acquires cores from the Polkadot Network, making them available for users to consume immediately. To ensure fairness and availability, the PDP interlaces these cores so that users can share a core and test the environment first. If satisfied, users can upgrade to a full core for maximum block production in a given cycle.
Next Cycle
When selecting this option, the PDP purchases a core on behalf of the project and assigns it directly to the project. This ensures the project becomes the sole owner of the core and gains additional benefits, such as fixed-price renewals and full block production capacity.
Comparing Options
Schedule Option | Right Now | Next Cycle |
---|---|---|
Availability | Immediate | When next cycle starts (max 28 days) |
Cost | Lower | Higher |
Block Production | ~2 minutes | ~6 seconds |
Automatic Renewal | No | Yes |
Ownership of core | No | Yes |