Support Tips/Tricks and maybe a Treat or two!
-
Our engineers will be online to answer questions, provide some tips, tricks, and whatever else you can throw at them.
-
Greg here from the support team! We created this space for the Scale Legion community members to ask questions, give comments and also for us to put out tips or tricks that you might benefit from. We will be putting out information weekly and check this daily. I would like to stress that if you are having an issue with you Scale cluster that you do call Scale support or send in a case.
-
Thanks Greg!
-
-
@ghoward said in Support Tips/Tricks and maybe a Treat or two!:
Check out this video on VM File Level Recovery!
Awesome stuff!
VM File Level Recovery? That's one amazing value add!
-
Linux Mint as a recovery platform, that's simple and very smart. Always keep a Linux Mint ISO on hand for this stuff, makes so many things so easy.
-
@Kelly said in Support Tips/Tricks and maybe a Treat or two!:
@blakerodier said in Support Tips/Tricks and maybe a Treat or two!:
Hey all. I wanted to talk about a topic that may be confusing for some users. Over-Provisioning CPUs for VMs.
Scale Computing’s HC3 system like any virtualization platform has physical limitations when it comes to CPU resources. Each node in a cluster has a physical limit to the number of physical cores and threads available to present to guest OSs. If you choose to you can allocate resources to your virtual machines based strictly on on the number of threads available on a physical node.
If you have two 8 core hyperthreaded processors in a node you will have 32 threads or logical CPUs you can assign for a 1 to 1 ratio on each node. In most instances there are CPU cycles that will go unused in a 1 to 1 setup. HC3 can utilize processor scheduling to allow for Over-Provisioning of CPUs meaning that for the same 32 threads that are present you could allocate 64 or 96 virtual CPUs and allow VMs to utilize idle cycles that would have been wasted in a 1 to 1 setup.
One restriction that is built into HC3 is that it will limit any individual VM to the number of threads available on the lowest capacity node in the cluster. If you have 2 nodes with 32 threads and 1 node with 16 threads, any one VM will only be able to allocate 16 virtual CPUs. This prevents any 1 VM from being unable to run if a livemigrate to another node happens and the VM tries to utilize all virtual CPUs. When deciding how to over-provision it is best to start with conservative numbers and build up if there are no issues. If you start seeing high CPU spikes or high wait times it may be important to turn down the amount of over-provisioning being used.
Available means physically (or logically I guess since they're hyperthreaded) on the nodes? So if you have identically spec'd nodes there shouldn't be an issue with over provisioning?
-ordering my first Scale cluster tomorrow
Lucky!
-
@Kelly said in Support Tips/Tricks and maybe a Treat or two!:
-ordering my first Scale cluster tomorrow
A perfect holiday gift idea for all of your techie loved ones! Or for yourself. Congrats!
