CirrusGrid is the only Cloud PaaS which can automatically scale any application, both vertically and horizontally, making hosting of your applications truly flexible.
Automatic vertical scaling is made possible by CirrusGrid’s ability to dynamically change the amount of allocated to server resources (RAM and CPU) according to its current demands, with no manual intervention required. This feature guarantees you never overpay for unused resources and saves your time due to eliminating the necessity of handling the load-related adjustments or architectural changes.
You simply decide the maximum limit you are ready to consume and CirrusGrid automatically defines the optimal amount of resources required for your app, tracking the incoming load in real time.
So, the key idea of automatic scaling is fairly simple – as soon as an application’s load grows, CirrusGrid simply makes additional resources available to it; and when the load goes down again, the resources get reduced by the platform automatically.
Herewith, the resources are allocated immediately without delays or negative impact on your application, which can be seen within the next video:
Tip: The vertical scaling feature is applicable for any type of instance in environment (i.e. application server, database, load balancer, Docker container, Elastic VPS, cache instance and build node).
As you could observe within the video above, CirrusGrid measures resources in special units called cloudlets, which provide you with a superior granularity while scaling. A cloudlet is roughly equivalent to 128 MiB RAM and 400Mhz CPU core.
There are two types of cloudlets available: reserved and dynamic.
Automatic vertical scaling is performed within the confines of the stated dynamic cloudlets number. You are able to choose your scalability limits with the appropriate settings and, in such a way, effectively put caps on the budget you are ready to spend, preventing unexpected or high bills.
You can combine the usage of both cloudlet types in different ways, following the most suitable for you pricing model.
A newly created environment receives a certain amount of cloudlets. Resource consumption depends on the type and quantity of your software stacks. Upon being added to the environment, each stack receives the default number of allocated cloudlets according to the optimal resource amount, required for its proper workability.
If you would like to change these values and scale your environment, the maximum number of available resources (cloudlets) can be increased/decreased manually through the Environment topology wizard. For that, use the cloudlet sliders in the Vertical Scaling section of its central pane.
Note: If changing the scaling limit (i.e. the number of the dynamic cloudlets) for the existing application server, database or cache nodes, the corresponding layer will be restarted. Herewith, the appropriate warning will be displayed directly in the topology wizard:
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.