All CPU Sockets not Utilized on Windows Server 2016

[exalate-issue-sync[bot]]

Reported by customer: "I am using an H2O cluster on a single machine with the following parameters

• Windows server 2016
• 4*E7-8890v3 (72 real cores, and 144 cores including HT) And I could see 36 cores only, and what's more - during the models training, H2O uses the neighboring cores (what means, that when for some physical cores both of HT logical cores as busy, and for some of cores, none of the logical cores are busy, and the real performance of such a setup even lower than a performance of 36 cores machine with disabled Hyper-threading)"

Reproduced on EC2 c5.18xlarge instance with 72 cores / 2 sockets / Windows Server 2016:

1. started h2o with java -jar -Xmx20G h2o.jar
2. in Flow, ran Airlines_Delay.flow with the full allyears.1987.2013.csv data set. !Screen Shot 2019-02-19 at 6.17.07 PM.png|thumbnail! !Screen Shot 2019-02-19 at 6.26.44 PM.png|thumbnail!

[exalate-issue-sync[bot]]

Nidhi Mehta commented: #93746 (https://support.h2o.ai/a/tickets/93746) - Only 36 cores are being used on a single host with 144 cores

[h2o-ops]

JIRA Issue Migration Info

Jira Issue: PUBDEV-6295 Assignee: Michal Kurka Reporter: Joseph Granados State: Open Fix Version: N/A Attachments: Available (Count: 2) Development PRs: N/A

Attachments From Jira

Attachment Name: Screen Shot 2019-02-19 at 6.17.07 PM.png Attached By: Joseph Granados File Link:https://h2o-3-jira-github-migration.s3.amazonaws.com/PUBDEV-6295/Screen Shot 2019-02-19 at 6.17.07 PM.png

Attachment Name: Screen Shot 2019-02-19 at 6.26.44 PM.png Attached By: Joseph Granados File Link:https://h2o-3-jira-github-migration.s3.amazonaws.com/PUBDEV-6295/Screen Shot 2019-02-19 at 6.26.44 PM.png