Deploy BETA CAE EPILYSIS on an Azure virtual machine

Azure Virtual Machines
Azure Virtual Network

Caution

This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the CentOS End Of Life guidance.

This article presents the performance results of running the BETA CAE EPILYSIS application on an Azure virtual machine (VM). EPILYSIS is a software program that's used to perform several types of finite element analysis on various structures and materials.

EPILYSIS is used in the aerospace, automotive, defense, high-tech, and industrial equipment industries. Engineers use EPILYSIS to help design and optimize products. EPILYSIS can be combined with other tools, such as ANSA and META, to optimize simulations. The solver covers various solution types, like structural, NVH (noise, vibration, and harshness), optimization, and more.

Why deploy EPILYSIS on Azure?

Deploy EPILYSIS on Azure to get benefits like:

  • Modern and diverse compute options to meet your workload's needs.
  • The flexibility of virtualization without the need to buy and maintain physical hardware.
  • Rapid provisioning.
  • Performance that scales as CPUs are added.

Architecture

Diagram that shows the architecture for running BETA CAE EPILYSIS on Azure.

Download a Visio file of this architecture.

Components

Compute sizing and drivers

The performance tests of EPILYSIS on Azure used an HBv3-series VM and Eadsv5-series VM running on a Linux operating system.

HBv3-series VMs are optimized for HPC applications, like fluid dynamics, explicit and implicit finite element analysis, weather modeling, seismic processing, reservoir simulation, and RTL simulation.

Eadsv5-series VMs are optimized for memory-intensive enterprise applications, such as relational database servers and in-memory analytics workloads.

The following table provides the configuration details for HBv3-series and Eadsv5-series VMs:

VM series VM size vCPU Memory (GiB) Temp storage (GiB) Max data disk Max NICs
HBv3 Standard_HB120-16rs_v3 16 448 2*960 32 8
HBv3 Standard_HB120-32rs_v3 32 448 2*960 32 8
Eadsv5 Standard_E64ads_v51 64 512 2400 32 8

1 Constrained core sizes available

EPILYSIS installation

Before you install EPILYSIS, you need to deploy and connect a Linux VM. Then you can download and install EPILYSIS.

EPILYSIS performance results

EPILYSIS version 23.1.1 was used for testing the 101_large_7million model.

The following table provides details about the computing environment that was used for testing.

VM series Operating system version Operating system architecture Processor MPI
Eadsv5 Linux CentOS 7.9 HPC Gen2 x86-64 AMD EPYC 7763v Open MPI 4.1.1
HBv3 Linux CentOS 7.9 HPC Gen2 x86-64 AMD EPYC 7V73X Open MPI 4.1.1

Important

The version of Linux discussed in this article will be discontinued in 2024. Tests that are performed on newer versions of Linux that include the same drivers are expected to produce similar results.

Model details

The 101_large_7million model is used for EPILYSIS solver validation. This model is set up for a linear static analysis (solution 101). A linear static analysis is an analysis where a linear relation holds between applied forces and displacements. The following image shows the 101_large_7million model.

Diagram that shows the 101_large_7million model.

The following table provides details about the model.

Model name Nodes Shell elements Solid elements
101_large_7million.nas 7678688 6341470 1295109

EPILYSIS performance results on a HBv3-series VM

The following table shows the details of each test on a HBv3-series VM. As the number of vCPUs increases, the total elapsed time decreases, and the relative speed increase improves.

VM size Number of vCPUs available Number of vCPUs used Total elapsed time (seconds) Relative speed increase
Standard_HB120-16rs_v3 16 1 5542 1.00
Standard_HB120-16rs_v3 16 2 3469 1.60
Standard_HB120-16rs_v3 16 4 2213 2.50
Standard_HB120-16rs_v3 16 8 1630 3.40
Standard_HB120-16rs_v3 16 16 1420 3.90
Standard_HB120-32rs_v3 32 20 1393 3.98

The following graph shows how the relative speed increase improves as you increase the vCPUs. It begins to plateau at 16 vCPUs.

Graph that shows the relative speed increase for the HBv3-series VM.

EPILYSIS performance results on Eadsv5-series VMs

The following table illustrates that as the number of vCPUs used increases, the total elapsed time in seconds decreases, and the relative speed increase improves significantly. There's a strong correlation between the vCPUs used and the efficiency of the process.

VM size Number of vCPUs available Number of vCPUs used Total elapsed time (seconds) Relative speed increase
Standard_E64ads_v51 64 1 6049 1.00
Standard_E64ads_v51 64 2 3480 1.74
Standard_E64ads_v51 64 4 2195 2.76
Standard_E64ads_v51 64 8 1520 3.98
Standard_E64ads_v51 64 16 1177 5.14
Standard_E64ads_v51 64 20 1122 5.39

1 Constrained core sizes available

The following graph shows how the relative speed increase improves as you increase the vCPUs.

Graph that shows the relative speed increase for the Eadsv5-series VM.

Azure cost

The following table provides estimated runtimes that you can use to calculate Azure costs. To compute the cost, multiply the estimated time by the Azure VM hourly rate. For the hourly rates for Linux, see Linux VMs pricing. Azure VM hourly rates are subject to change.

The cost calculations only factor in the simulation runtime. The installation time, simulation setup time, and software costs aren't included. You can use the Azure pricing calculator to estimate VM costs for your configurations.

VM size vCPUs used Elapsed time (hours)
Standard_HB120-16rs_v3 1 1.54
Standard_HB120-16rs_v3 2 0.96
Standard_HB120-16rs_v3 4 0.61
Standard_HB120-16rs_v3 8 0.45
Standard_HB120-16rs_v3 16 0.39
Standard_HB120-32rs_v3 20 0.39
Standard_E64ads_v51 1 1.68
Standard_E64ads_v51 2 0.97
Standard_E64ads_v51 4 0.61
Standard_E64ads_v51 8 0.42
Standard_E64ads_v51 16 0.33
Standard_E64ads_v51 20 0.31

1 Constrained core sizes available

Summary

  • The HBv3-series and Eadsv5-series VMs on Azure were used to create a benchmarking suite, which is one of the many uses of EPILYSIS.

  • EPILYSIS's performance was evaluated on two HBv3-series VMs (Standard_HB120-16rs_v3 and Standard_HB120-32rs_v3) and one Eadsv5-series VM (Standard_E64ads_v5).

  • On the HBv3-series VM, there's a 400% performance improvement when the vCPU count is increased to 20 vCPUs. A single vCPU is used as a baseline.

  • Similarly, on the Eadsv5-series VM, there's a 500% performance improvement when the vCPU count is increased to 20 vCPUs. A single vCPU is used as a baseline.

  • According to a validation study, the performance of a Eadsv5-series VM with 20 vCPUs is 19% more efficient compared to a HBv3-series VM with the same number of vCPUs.

Contributors

This article is maintained by Microsoft. It was originally written by the following contributors.

Principal authors:

Other contributors:

To see non-public LinkedIn profiles, sign in to LinkedIn.

Next steps