This article covers base cores, burst cores, standard true ups, locked true ups, and other key considerations for core capacity planning.

Cloudmersive customers have several models to consider when planning core capacity for Managed Instance and Private Cloud deployments. These core capacity options are important to understand, as they directly impact the scalability of Cloudmersive solutions.

Base cores

Base cores are “normal” CPU cores deployed onto Cloudmersive Managed Instance and Private Cloud nodes. Base cores can typically process 2 or more concurrent requests; the exact number depends on the request complexity and the response time.

Base cores are utilized at any time. If incoming requests exceed the volume that any given base core can handle concurrently, these requests will be queued and not handled concurrently.

Burst cores

Burst cores are added to deployments after customers already have 2 or more base cores active. They’re an autoscaling option licensed based on the percentage volume of their capacity the customer actually utilizes. Standard burst core utilization tiers are 25%, 50% and 75%.

The burst core licensing model is ideal for supporting enterprise traffic patterns with large, disproportionate spikes in activity at certain times, such as day-time traffic increases when users sign on to a platform or month-end traffic increases when invoices are processed.

Burst Core True Ups

True ups account for burst core utilization percentages which exceed the amount originally licensed. Cloudmersive offers Standard and Locked true ups.

Standard True Ups

Standard true ups allow customers to continue using more than the utilization percentage that was originally licensed to them. This means, for example, that customers licensed at 25% utilization would upgrade to the 50% utilization tier once their utilization percentage reached 26%. The incremental cost of that upgrade would be reflected at the end of the invoice period.

Locked True Ups

Locked true ups prevent customers from consuming more than their licensed utilization percentage. This ensures customers will not have any unexpected overage costs at the end of the invoice period.

Key Considerations

When planning core capacity for new or existing deployments, customers should carefully consider their expected request volume, unique traffic patterns, and expected application growth over time. They should also bear response times and API request complexity in mind, along with any additional factors unique to their environment.

For further clarification or advice about planning core capacity for Cloudmersive deployments, please contact a member of our team for a consultation.