Short answer: Load less, rebuild less and draw less. Open with Large Design Review or Lightweight mode when you don't need full feature data. Use simplified (SpeedPak or defeatured) configurations of complex purchased parts. Fix mate problems so the assembly rebuilds less. Use subassemblies set to rigid, and turn down graphics settings such as image quality and RealView. Then find the actual bottleneck with Performance Evaluation (formerly AssemblyXpert) instead of guessing.
Where the time goes
A large assembly gets slow for four main reasons:
1. Loading: many files, large files, or files resolved across a slow network.
2. Rebuild: mates, in-context references and assembly features that have to be solved again.
3. Graphics: a high triangle count, high image quality, transparency and RealView.
4. Detail in purchased models: valves, connectors and motors downloaded with full internal detail, threads and text.
Steps
1. Measure first. Run Tools > Evaluate > Performance Evaluation. It lists slow-opening files, rebuild times, and graphics-heavy parts and mate issues.
2. Choose the right open mode.
- Large Design Review: the fastest. Use it for viewing, measuring and reviewing, and selectively load parts to edit.
- Lightweight: loads a subset of the model data and resolves components when needed.
- Large Assembly Settings: set the component-count threshold so that large-assembly behavior turns on automatically.
3. Simplify heavy parts. Make a "simplified" configuration that suppresses internal features, cosmetic threads, text and fillets, and use it in the top-level assembly. SpeedPak configurations of subassemblies keep only the selected faces for mating.
4. Make subassemblies rigid unless you need motion. Rigid subassemblies are solved as one body.
5. Clean up mates.
- Mate to reference geometry (planes, axes) in key components where it makes sense.
- Avoid long chains of dependent mates and circular references.
- Resolve every mate error and warning. A broken mate makes SOLIDWORKS try to solve it again.
- Use the Mate Diagnostics or MateXpert tool for conflicts.
6. Limit in-context references. Lock or break external references once the design is stable. Use List External References to find them.
7. Turn down graphics. Lower the image quality (shaded and draft quality), turn off RealView and shadows, and hide what you don't need with display states.
8. Keep files local or on a properly configured PDM vault, not on an unmanaged network share with many broken or redirected references.
9. Use patterns and component instances wisely. Component patterns are generally lighter than many separately mated copies.
Worked example
A frame-and-gas-box assembly with a few thousand components takes several minutes to open and lags on rotation.
1. Performance Evaluation shows three downloaded valve models with very high graphics triangle counts and full internal detail, plus a rebuild warning on a gas stick subassembly.
2. The engineer creates a "simplified" configuration for each valve with internal features suppressed and cosmetic threads off, and sets the top-level assembly to use it.
3. The gas stick subassembly is set to rigid, and its failing mate (to a face that was rebuilt away) is replaced by a mate to the valve's reference plane.
4. Image quality is lowered and RealView is turned off for working sessions.
5. The team opens the top-level assembly in Large Design Review for reviews and resolves only the module being edited.
Open time and rotation lag both drop noticeably. Most of the gain came from the three valve models and the mate repair, which is typical: a few components usually cause most of the slowdown.
Common mistakes
- Upgrading hardware first without measuring. Bad models are slow on any workstation.
- Leaving mate errors "for later." They cost rebuild time every time.
- Inserting vendor models as-is with full internals and embossed text.
- Flexible subassemblies everywhere.
- Overusing in-context design in final assemblies.
- Unmanaged copies of library parts, which create duplicate files and confusing references. (For copying assemblies, see our Pack and Go article.)
Team habits that keep assemblies fast
- A library standard: every purchased model enters the library with a simplified configuration already made, so nobody has to fix it again in each project.
- Mate conventions: agree how modules mate to the frame, for example to named reference planes. Assemblies then rebuild predictably and can be swapped.
- A module boundary rule: each module is a subassembly with its own owner and its own acceptance check. The top level only carries module-to-frame mates.
- A regular health check: run Performance Evaluation at each design review and treat new rebuild warnings as review items.
- Display states for reviews: prepare display states (for example "frame only," "gas box," "full") so reviewers don't load everything.
FAQ
Lightweight vs Large Design Review?
Lightweight still lets you edit the assembly with partial data. Large Design Review is mainly for viewing and review, with selective editing.
Does SpeedPak break the BOM?
No. SpeedPak configurations keep the BOM information while reducing the graphics and geometry loaded.
Should I use defeature?
Yes, for parts you share or use as placeholders. Defeature creates a simplified version that hides internal detail.
Is a GPU upgrade worth it?
Only after you have fixed model-side problems. Use a certified graphics card and driver for stability.