Need some advice on cpu core number vs memory for ece allocator

[rockybean]

Hi,
I'm applying new test machine for ece and get below specification.

CPU 24 Core/ Memory 384 GB

As I know, ece allocate same cpu ratio to node with memory.

For example, If I create a 64GB Node, then ece will allocate 24*(64/384) = 4 CPU Core to this node.

But 4 cpu core is too small comparing to 64GB memory.

So any advice on this kind of machine specification?

Should I limit allocator available memory by --capacity parameter?

And what is the ideal cpu core to memory size ratio? like 64Core to 256GB?

thanks!

[Alex_Piggott]

In general we recommend trying to keep the cpu:mem ratio in the 1:8 range (that's a typical ratio you'll see in standard AWS hardware) and we have observed issues with smaller clusters not being able to load with 1:11 or worse (the temp fix is described below and there's a full fix coming in 2.2 or 2.3)

There's a few workarounds:

• As you point out you can artificially restrain the allocator capacity .... this makes most sense if you have no control over how the capacity will be used, since in that case you could have 6x 64GB instances all maxing out their CPU
• You can disable the hard_limit (set to false) in the advanced cluster data section - this will allow clusters to use all the CPU (and it shares out CPU in the right ratio when the box is overprovisioned)
  • there is an undocumented API call we've been giving out via support to let you make that the default (in my opinion this is the most desirable configuration for many ECE deployments, ie providing extra performance in return for making it less predictable)
• You can keep the hard limit but up the CPU overcommit factor (defaults to 1.2) ... there's a post in here where I describe how to set that, it should be easily searchable.

But if you're not going to be using the capacity then restricting the allocator capacity makes the most sense (especially given licensing costs), and if you are using the capacity then you need a plan for managing over-provisioning anyway

Alex

[rockybean]

Thanks!
Do you mean below post?

ECE RAM to Storage Ratio

@IanGabes The 2 other "override" fields that have proven useful so far are: "resources": { "cpu": { "hard_limit": true } }, If you set hard_limit to false then the cluster gets the entire CPU of the host instead of a sub-set determined by its size. Obviously this is not without risk to the overall platform stability "overrides": { "resources": { // (needed for 1.1+) "cpu": { "factor": 1.3 } } }, A safer way of boosting the CPU for a given…

[Alex_Piggott]

Yep that's the one