This is an old revision of the document!
2019 GPU Expansion
Ok, we try this year. Here are some informational pages.
- P100 vs GTX & K20 page
- 2019 GPU Models page
| Option | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | |
|---|---|---|---|---|---|---|---|---|---|
| Nodes | U | ||||||||
| Cpus | |||||||||
| Cores | physical | ||||||||
| Gpus | |||||||||
| Cores | cuda | ||||||||
| Cores | tensor | ||||||||
| Tflops | cpu dpfp | ||||||||
| Tflops | gpu spfp |
Exxactcorp: For the GPU discussion, 2 to 4 GPUs per node is fine. T4 GPU is 100% fine , and the passive heatsink is better not worse. The system needs to be one that supports passive Tesla cards and the chassis fans would simply ramp to cool the card properly, as in any passive tesla situation. Titan RTX GPUs is what you should be worried about, and I would be hesitant to quote them. They are *NOT GOOD* for multi GPU systems.
Microway: For this mix of workloads two to four GPUs per node is a good balance. Passive GPUs are *better* for HPC usage. All Tesla GPUs for the last 5? years have been passive. I'd be happy to help allay any concerns you may have there. The short version is that the GPU and the server platform communicate as to the GPUs temperature. The server adjusts fan speeds appropriately and is able to move far more air than a built-in fan would ever be able to.
ConRes: In regards to the question around active vs. passive cooling on GPUs, the T4, V100, and other passively cooled GPUs are intended for 100% utilization and actually can offer better cooling and higher density in a system than active GPU models.
Summary
Lets amend this request [to vendors]. I realize with 100k we might be only talking about 4-6 boxes. I can handle all the software. Would be nice if all nodes did have centos7+cuda installed. Not required but let me know.
— Henk 2019/09/03 08:55
We are embarking on expanding our GPU compute capacity. To that end we tested some of the new GPU models. During a recent users group meeting the desire was also expressed to enable our option to enter the deep learning (DL) field in the near future. We do not anticipate to run Gaussian on these GPUs so are flexible in the mixed precision mode models. The list of software, with rough usage estimates and precision modes, is; amber (single, 25%), lammps (mixed, 20%), gromacs (mixed, 50%) and python bio-sequencing models (mixed or double, < 5%).
We anticipate the best solution to be 2-4 GPUs per node and not an ultra dense setup. Job usage pattern is mostly one job per GPU with exclusive access to allocated GPU, albeit that pattern may change based on GPU memory footprint. We were zooming in on the RTX 6000 or TITAN GPU models but are open to suggestions. The T4 looks intriguing but the passive heat sink bothers us (does that work under near constant 100% utilization rates?).
We do not have a proven imaging functionality with CentOS7, Warewulf and UEFI booting so all nodes should be imaged. Software to install is latest versions of amber (Wes to provide proof of purchase), lammps (with packages yes-rigid, yes-gpu, yes-colloid, yes-class2, yes-kspace, yes-misc, yes-molecule), gromacs (with -DGMX_BUILD_OWN_FFTW=ON). All MPI enabled with OpenMPI. Latest Nvidia CUDA drivers. Some details if you need them at this web page: https://dokuwiki.wesleyan.edu/doku.php?id=cluster:172
DL software list: Pytorch, Caffe, Tensorflow.
Wes to install and configure scheduler client and queue.
Wes to provide two gigabit ethernet switches.
Compute nodes should have 2 ethernet ports, single power ok but prefer redundant, dual CPUs with optimized memory configuration around 96-128 Gb. Start IP address ranges; nic1 192.168.102.89, nic2 10.10.102.89, ipmi 192.168.103.89, netmask 255.255.0.0 for all.
Wes will provide 208V powered rack with 7K BTU cooling AC. Standard U42 rack (rails at 30“, up to 37” usable). We also have plenty of shelves to simply hold the servers if needed. Rack contains two PDUs (24A) supplying 2×30 C13 outlets. External Link
