Abaqus Release 6.9 Performance Data

The Abaqus benchmark problems are intended to provide an estimate of the performance that can be expected when running representative Abaqus analysis jobs on different computer platforms. The different Abaqus products and different types of Abaqus analyses are appropriate for different classes of machines and stress machines differently. The benchmarks are organized with the intention of making it possible for users to view the subset of the benchmark data appropriate to their usage of Abaqus.

The benchmark problems listed here are available upon request. If you are a customer, see Abaqus Answer 2342 for instructions on obtaining the input files associated with these benchmark problems. If you are a hardware vendor and would like to submit performance data please contact .

NOTE: The Abaqus benchmark problems may change between releases. Therefore the timing data presented on these pages should not be directly compared with benchmark data obtained using other Abaqus releases.

All times are given in seconds and include the time required for the main analysis executables (standard.exe and explicit.exe), the analysis input file processor (pre.exe), and the Abaqus/Explicit packager (package.exe).

Organization of the Benchmarks

	Hardware Categories
	Abaqus Job Categories
	Presentation of Benchmark Data

	Abaqus/Standard Benchmark Problems
	Abaqus/Explicit Benchmark Problems

Workstation Benchmark Data

Server Benchmark Data

	Abaqus/Standard Server Benchmark Data
	Abaqus/Explicit Server Benchmark Data

Organization of the Benchmarks

The Abaqus benchmark suite is designed with the intent of providing users of Abaqus information about how Abaqus will perform on various hardware platforms available on the market. As different Abaqus jobs will stress the hardware in different ways, providing a benchmark suite that is both comprehensive and relatively easy to understand is a challenging task. In order to make good use of the data on this page, users should be careful to understand how the benchmarks are organized and to use data that is representative of their problems.

There are two basic variables a user needs to consider when looking at benchmarks. The first is the type of Abaqus job. Different Abaqus jobs stress hardware in different ways. A user running eigenvalue analyses with Abaqus/Standard will want to focus on different aspects of a hardware purchase than a user running an electronics drop test with Abaqus/Explicit. The second variable a user must consider is the type of hardware being considered. In the following section the basic categories of Abaqus job and hardware used in presenting benchmark data are described.

Hardware Categories

• Workstation: The first hardware category is workstations. Typically workstations have either 2 or 4 cores and sit on a user's desktop. Workstations are typically used for running jobs that do not run for a very long time (over night being the maximum) or use a very large amount of memory. Workstations are typically configured with 2, 4, or possible 8 GB of physical memory. In a typical workstation configuration a user is likely to be doing a number of things on the machine at the same time. During the time that the 6.7 release is in use, it is anticipated that quad-core workstations will become widely available, and users may start to have 2P/quad-core (8 cores total) workstations.

• Compute Server: The second hardware category is compute servers. Computer servers are machines that are dedicated to computing long-running or large Abaqus jobs as efficiently as possible. In past years compute servers were large SMP machines that were typically shared between many users. More recently users have been migrating to having a farm of SMP compute servers each of which runs a single Abaqus job at a time. This has also led into the more recent usage of clusters, which means dedicating multiple compute servers to a single Abaqus job. Compute clusters typically feature a high-speed private network which connects the servers. While the trend has been away from multi-user servers, this model is by no means extinct. Readers should note that compute clusters are typically configured to function as a single multi-user server, but this is a server that physically consists of a number of compute hosts each of which will be dedicated to a single task at any time.

Benchmark Problem Descriptions

Abaqus/Standard Benchmark Problems

Click the link above to expand the Abaqus/Standard problem descriptions below which provide an estimate of the performance that can be expected when running Abaqus/Standard on different computers. The jobs are representative of typical Abaqus/Standard applications including linear statics, nonlinear statics, and natural frequency extraction.

Abaqus/Explicit Benchmark Problems

Click the link above to expand the Abaqus/Explicit problem descriptions below which provide an estimate of the performance that can be expected when running Abaqus/Explicit on different computers. The jobs are representative of typical Abaqus/Explicit applications including high-speed dynamic impact events and quasi-static events with complicated contact conditions. The number of increments listed in the tables below are approximate and can vary somewhat depending on the hardware platform and the number of parallel domains.