Reducing the amount of work being done on CPU

From: Maxime Boissonneault (maxime.boissonneault_at_calculquebec.ca)
Date: Tue Sep 01 2015 - 09:48:24 CDT

• Next message: Lara rajam: "parameters problem in sulfated molecules"
• Previous message: Brian Radak: "LJcorrection + switching?"
• Next in thread: Norman Geist: "AW: Reducing the amount of work being done on CPU"
• Reply: Norman Geist: "AW: Reducing the amount of work being done on CPU"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi,
We have received very fat GPU nodes, which have 16 GPUs (8 x K80), and 2
12-core sockets (24 CPU cores).

While I got a rather good scaling with the ApoA1 benchmark on nodes with
8 x K20 + 2 x 10-core sockets (scaling was almost perfect between 1 GPU
+ 2 cores and 8 GPUs + 20 cores), the scaling is not nearly as
impressive on our very fat nodes.

I suspect the reason is because the low number of CPU cores per GPU is
becoming a bottle neck.
Is there any setting I should chnage in the benchmark to bias more
workload toward the GPUs rather than the CPUs ?

Thanks,

-- 
---------------------------------
Maxime Boissonneault
Analyste de calcul - Calcul Québec, Université Laval
Instructeur Software Carpentry
Président - Comité de coordination du soutien à la recherche de Calcul Québec
Ph. D. en physique

• Next message: Lara rajam: "parameters problem in sulfated molecules"
• Previous message: Brian Radak: "LJcorrection + switching?"
• Next in thread: Norman Geist: "AW: Reducing the amount of work being done on CPU"
• Reply: Norman Geist: "AW: Reducing the amount of work being done on CPU"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.6 : Tue Dec 27 2016 - 23:21:17 CST