What is the best way to convince management that virtualization is not always appropriate in production?

I work in a small company with a .NET product, which was acquired by a mid-sized company with large iron products. Recently, a small part of the company acquired another small company with a similar .NET product, and management went to look at their technology. They actively use virtualization in their production environment, and it was decided that we will too.

Our product was not designed to work in a virtual environment, but some numbers may be made. For instance; There are times when we are associated with resources due to processes initiated by the client. This initiation is bursty in nature, but processing can be made asynchronous and throttle. In any case, this must be done for scalability.

But there is another treatment that we do that is not easily modified, because we are limited in resources for long periods of time.

How can I convince management that using virtualization is largely inappropriate for us?

+3
source share
3 answers

(), , . , . . , " ". , , . " ". , . , , , . , . .. ..,. ?

, . , , $$$ , ( ).

+8

, , .

, - 5 , 10-15% CPU , 50-75% CPU 25-50% "" .

"" , (, VM # 1 , CPU 3Ghz) , .

, 20 , CPU, . , Ghz, , VM . , , , . .

, .

+3

, .

Do some tests on platforms of various sizes and establish an approximate rule. If possible, do not say "this is the minimum necessary"; it’s better to say “with X resources, we make Y work units per hour, with X”, we do Y. A host that costs Z $ can hold W virtual machines of X resources, then bean counters will have beans to count. If in the end they decide that virtualization is economical, they may be right.

+2
source

Source: https://habr.com/ru/post/1741023/


All Articles