What is better - all sites on the same server or shove them all into VMs?

Question

Virtualization

It is possible to buy a real server inexpensively and connect it to colocation.
1. The question is actually this - there is a pool of sites of various subjects that I manage, there are about 10 of them, all with a maximum attendance of 500 uniques per day and sometimes even less (these are business sites, the owners bring normal profits, everything is fine) - I should place them on one server or create several virtual machines using KVM and cram them into VMs?
I want to somehow protect them all from each other and play with test sites in virtualization, to feel the spirit of the times, so to speak. :)

2. The second question - I wanted to jump from Hetzner to Yandex VM, but for the first time, they are not competitors at all in terms of prices and this topic alerted me - (see screenshot)
But how much% of the processor is guaranteed to be in my VM?
And how much, for example, do I now receive from the same Hetzner? Does anyone have such data?
Now we are working on Hetzener under KVM, I'm interested in the real% of the capacities allocated to me.

And returning to my question number 1 - if I put all the sites on my personal server, then everything will be fair, right? :) i.e. all the resources of an honest server will be distributed between the conditional 10 sites?

Answer 1

You look at Docker
, you will develop, and songs with updates-inheritances will begin, transfer - return, addition
in general, Docker what
VM needs is also not bad when there is a lot of legacy (there is a forum, wordress is still unhacked, etc.), evaluate years later 3-5, when you just operate "site there - site here", without looking for progers for "collect-raise",
shit - do not overlook the growth of the base and design it correctly

Answer 2

1) If the sites are pure HTML, then virtual sites are better inside one server, without virtual machines. If there are scripts there, then it is better to spread them over virtual machines or dockers for safety.
As a rule, scripts store their data in a database. Take care that scripts from one virtual machine cannot crawl into data (stored in the database) of another virtual machine. This can be done in the form of separate DBMS for each site. And it is possible - in one DBMS with access rights to the data in a DB.
If you want to train in virtual machines, then train on them. Basically, it's a good thing.
3) The concept of "honesty" in this context is very conditional and non-trivial. It is usually very different from the everyday meaning of the word.
The allocation of computing resources is a very complex topic. Especially with systems with multi-level caching - and modern computers are exactly like that. Study the concept of "Real Time" - it is unlikely that it will come in handy in practice right now, but it is very useful to have an understanding.

Answer 3

Scatter of course on virtual machines and containers

Answer 4

10 pieces, all with a maximum attendance of 500 uniques per day and sometimes even less

A modest VDS is enough for this. Why colocation?