5 Tips to Make NX Nastran Faster

By Amy Reyes

NX Nastran can be optimized to run simulations faster, but how? If you think processor speed is the main factor you should consider, think again. Degrees of freedom (DOF) are also not as important to Nastran speed as many simulation analysts would guess. So what has the biggest impact on NX Nastran solve times?

Input/output (I/O) according to Dr. Paul Blelloch, director of aerospace analysis for ATA Engineering, in a presentation he gave at the Siemens CAE & Test Symposium back in October.

We’ll look at five easy ways you can improve performance in NX Nastran starting with I/O.

  1. Nastran Best Practices.jpgLocate SCRATCH and SCR300 files on the fastest memory.
    When it comes to I/O, SCRATCH and SCR300 files have the most. These are going to be the areas you want to target in order to improve solving speed. Luckily you can specify a location within NX Nastran for high I/O files. If you have a large amount of RAM (at least 128 GB), your best bet is to locate the files there. Another good option is a solid state drive (SSD).

  1. Set parameters within the RCF file, command line, or options window.
    There are a few parameters that let you control the I/O in NX Nastran. You’ll want to use these when optimizing for speed. SCR controls how much data is written to the DBALL database compared to the SCRATCH and SCR300 files. The fastest option is SCR = YES. Everything will be written to the SCRATCH files, but beware! If you choose this option you can’t restart. Smem lets you determine how much RAM to dedicate to the SCRATCH files. The more RAM, the faster your simulation will be.

  1. Minimize the Front Size.
    Front Size, or the maximum length of a non-zero column in a matrix after it is reordered, plays a big role in how long it takes to solve. The bigger the Front Size, the longer it will take, so you’ll want to use the reordering algorithms in NX Nastran to minimize the Front Size of your model. NX Nastran will by default choose either the BEND or METIS algorithm based on the number of 3D elements in your model, but remember, the algorithms aren’t perfect. If you’re seeing slower speeds, you might want to try switching from one algorithm to the other.

FEA Solver NX Nastran.jpg4. Choose the right operating system.
Your operating system can also impact the amount of time a solve takes, so be sure to review all the options out there and choose the best one for your needs. NX Nastran typically performs better on Linux due to the way the OS handles memory, so Dr. Blelloch recommends Linux if you’re looking to reduce your runtime.

  1. Compare versions of NX Nastran.
    Finally, understand the differences between versions of NX Nastran—and know which version will be best at lowering your solve times. NX Nastran ILP has a few advantages over LP. For one, it has unlimited RAM. (Remember #1 where we talked about how important RAM is?) LP on the other hand has only 8GB RAM. Add to that the fact that ILP has 64-bit integers (compared to LP’s 32-bit integers) and you start to see the benefit ILP offers you. More integers won’t necessarily affect your runtime, but it will improve accuracy. 

Nastran Versions.jpg

So there you have it. Have you found any ways to make NX Nastran faster? Let us know down in the comments below! 

For more information on improving performance in NX Nastran, read the full article this post is based on, and check out Dr. Paul Blelloch’s presentation from the 2014 Siemens CAE & Test Symposium in which these tips—and more!—are located.

This article first appeared on the Siemens Digital Industries Software blog at