Content deleted Content added
m Tule-hog moved page Elasticity (system resource) to Elasticity (computing): alternate disambiguator |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
(3 intermediate revisions by 3 users not shown) | |||
Line 1:
{{short description|Degree to which a computer system can adapt to workload changes}}
{{redirect|Elastic computing|the physical property|Elasticity (physics)|the economics measurement|Elasticity (economics)}}
In [[computing]], '''elasticity''' is defined as "the degree to which a system is able to adapt to workload changes by provisioning and de-provisioning [[System resource|resources]] in an [[Autonomic computing|autonomic]] manner, such that at each point in time the available resources match the current demand as closely as possible".<ref>{{cite
In the world of [[distributed system|distributed systems]], there are several definitions according to the authors, some considering the concepts of [[scalability]] a sub-part of elasticity, others as being distinct.
Line 18 ⟶ 19:
===Resources provisioning time===
One potential problem is that elasticity takes time. A cloud virtual machine (VM) can be acquired at any time by the user; however, it may take up to several minutes for the acquired VM to be ready to use. The VM startup time is dependent on factors, such as image size, VM type, data center ___location, number of VMs, etc.<ref name="vmstartuptime2012">{{cite book|last=Mao|first=Ming|author2=M. Humphrey|title=2012 IEEE Fifth International Conference on Cloud Computing |chapter=A Performance Study on the VM Startup Time in the Cloud |year=2012|doi=10.1109/CLOUD.2012.103|isbn=978-1-4673-2892-0|page=423|s2cid=1285357 }}</ref> Cloud providers have different VM startup performance. This implies any control mechanism designed for elastic applications must consider in its decision process the time needed for the elasticity actions to take effect,<ref>{{cite book|last=Gambi|first=Alessio |author2=Daniel Moldovan |author3=Georgiana Copil |author4=Hong-Linh Truong |author5=Schahram Dustdar
===Monitoring elastic applications===
Line 24 ⟶ 25:
===Elasticity requirements===
When deploying applications in cloud infrastructures (IaaS/PaaS), requirements of the stakeholder need to be considered in order to ensure proper elasticity behavior. Even though traditionally one would try to find the optimal trade-off between cost and quality or performance, for real world cloud users requirements regarding the behavior are more complex and target multiple dimensions of elasticity (e.g., SYBL<ref>
===Multiple levels of control===
Cloud applications can be of varying types and complexities, with multiple levels of artifacts deployed in layers. Controlling such structures must take into consideration a variety of issues, an approach in this sense being [http://www.infosys.tuwien.ac.at/research/viecom/SYBL rSYBL].<ref>
==See also==
|