Simulation Performance

What the simulation costs to run, and what it gives up when it is made cheaper. Two settings account for nearly all of it — the mesh resolution and the number of steps — and they bottleneck independently, so making a run faster starts with knowing which of the two is currently in the way.

Ordered from the machine doing the work to the setting chosen before the run starts, and the estimate made before the project is built.

• CPU Usage During Simulation — Why a run is slow while the CPU is not saturated: single-threaded geometry removal against multi-threaded physics, and the two independent cost drivers
• Mesh Resolution — Choosing a mesh width: what it costs in run time, how little it moves the physics, and the one kind of geometry it can make disappear
• Memory Planning — Estimating a run's memory from the NC program and the workpiece before building the project: which of the two rules it, the part no resolution can lower, and choosing the width against the machine's memory

See Also

• Machine Capability — the ceilings of the machine being simulated, as opposed to the workstation simulating it