Version 8.0 has the following enhancements over Version 7.1:

Support for the nVidia A100 GPU

The new A100 GPU offers over twice the performance of the current V100. Bencmarks testing systems wityh 8-A100s have achieved over 100 Tflops. It is important to run the version of FMS corresponding to the driver on your system. A list of the appropriate drivers is containd on the Download page.

Automatically configure CPUs to skip hyperthreads (Linux)

"Processors" on Linux systems may point to a physical core or be hyperthreads, which run in parallel on the same cores. All routines in FMS are designed to use all the reasources on each physical core. Scheduling additional processors on the same hardware degrades performance.

On startup FMS analyzes the CPU configuration and identifies the sockets (physical chip) and cores within each chip for each processor. When a processor is found that uses the same socket and core as a previous one, it is identified as a hyperthread. The maximum number of physical cores found is used to set the FMS Parameter MAXCPU.

The CPUS page displayed by Dashboard displays detail information about each processor, including the socket number, core nmber and if it is a hyperthread.

Memory to GPU bandwidth test (Linux)

Achieving maximum performance with FMS requires a fast and uniform transfer of data between memory and each GPU. FMS now contains the functionality to perform these tests. The FMS Parameter CGTEST is used to control which tests are performed. The FMS Parameter CGMPCT determines the percent of GPU memory used in the transfers and the FMS Parameter CGLOOP determines the number of times each test is repeated.

Dashboard now contains a CPU-GPU page, which lists the results of these tests.

Environment variable FMSGPUEND

FMS is designed to run on systems both with and without GPUs. On startup hardware and software are examined to determine if every component necessary to run with GPUs is available. If all the conditions are met, GPUs are used. However if any required component is missing, FMS continues without using GPS. Wnen set, this environment variable instructs FMS to exit rather than continue without GPUs.

Environment vairable FMSTIMEOUT

When set, this value specifies the maximum seconds FMS can run. When this value is exceeded, execution stops. If it is not set, FMS runs to completion.