Clients are increasingly migrating to the cloud in pursuit of flexibility: it is much easier to add disk, memory and processors here if something is missing. But sometimes newbies find that adding resources doesn't help. The speed of work does not increase, and problems begin with backup and recovery.
Today, together with @kvolodin, we will share why the infinite increase in VM resources can harm users and how to plan for performance gains in obvious but powerful ways. The article is useful for those who have moved or are planning to move to the cloud and are still getting acquainted with the nuances of the cloud environment.
Obvious reasons: hardware limitations and backups
Now in our cloud, adding resources over the limit can be limited at the software level. If someone tries to go outside, they will immediately receive a message in the Cloud Director interface:
But it was not always so. In older versions of vCloud Director, we could not rigidly limit some parameters and prescribed limits only in the contract. Unfortunately, sometimes the information from the contract did not even reach the client's engineers, and they could feel the consequences on their own skin.
20 16 . Veeam Backup&Replication. 16 , . Veeam , . , . , .
. . , IaaS . , .
40 , 20 . 30 . , , , .
. , - . - , . . , .
. . - , .
, .
, . . .
. . , . . , ββ . : , .
. , 100%. , , . . .
, β β. 24 , .
. vCloud Director. . , . , . , .
. .
. . , . , .
, , .
, , , . Enterprise- - 24/7 . , .
, , SATA-. CPU, .
. : , . : .
β . ββ ββ. ββ , ββ .
, . , , .
. , . , , .
. : NetApp 16 .
-.
, .
CPU
IOPS
, IOPS: /. :
.
, , - .
.
, . IOPS IOPS .
. , .
. .
. .
: , . , .
, . , 8 , 4 2 . .
. . , .