Hello @all
I am actually testing a cluster environment where the nodes have 64GB of RAM and I am allocating arround 64GB to KVMs. Now ZFS configured to use 8GB, of course there is not enough RAM for all KVMs.
This is where KSM should come in to play.
KSM is activated the ksmtuned works and after arround 15-20min it starts to share RAM (of course you need to reach 80% usage).
My question now is, how you guys use to start your KVMs at a node reboot? Do you just start the half of the KVMs and then wait for KSM to start to work (to be exact, you would need to run exactly as much KVMs to reach 80% RAM usage so that KSM starts). And then start the rest of the KVMs?
This way starting KVMs would take arround 20-30min. That is not really good.
Otherwise starting all KVMs at once do result in a node crash and reboot on my test environment. So this is also not the way to go
Thanks for any suggestion
I am actually testing a cluster environment where the nodes have 64GB of RAM and I am allocating arround 64GB to KVMs. Now ZFS configured to use 8GB, of course there is not enough RAM for all KVMs.
This is where KSM should come in to play.
KSM is activated the ksmtuned works and after arround 15-20min it starts to share RAM (of course you need to reach 80% usage).
My question now is, how you guys use to start your KVMs at a node reboot? Do you just start the half of the KVMs and then wait for KSM to start to work (to be exact, you would need to run exactly as much KVMs to reach 80% RAM usage so that KSM starts). And then start the rest of the KVMs?
This way starting KVMs would take arround 20-30min. That is not really good.
Otherwise starting all KVMs at once do result in a node crash and reboot on my test environment. So this is also not the way to go
Thanks for any suggestion
