Solution Number: 830
Title: Handling large models
Platform: All Platforms
Applies to: All Products
Versions: All versions
Categories: Error Messages, Solver
Keywords: mesh geometry memory java heap space

Problem Description

Models with many domains, boundaries, and physics features are slow to work with.

Solution

Large models can contain hundreds or even thousands of domains, boundaries, and physics features. Such a large number of features within the model can adversely affect performance. The models themselves may not take an excessive amount of memory to solve, but if they do result in any Out of memory messages, then first consult Knowledge Base 1030 for guidance. This Knowledge Base article addresses models which are solvable, but are large and slow to work with.

Complex graphical visualization of the model data benefits from having a graphics card with more memory. A list of support graphics cards is posted on the System Requirements Page. Make sure that your graphics card drivers are up to date. Use either DirectX or OpenGL rendering rather than Software rendering for optimal graphics performance. Instructions on how to change the rendering are in Knowledge Base 933. If possible, minimize your usage of transparency in 3D models since this increases the amount of data visualized at once.

Handling large models can lead to that you run out of Java Heap Space. For information about how to tune your Java Heap, please see Knowledge Base 1243


Disclaimer

COMSOL makes every reasonable effort to verify the information you view on this page. Resources and documents are provided for your information only, and COMSOL makes no explicit or implied claims to their validity. COMSOL does not assume any legal liability for the accuracy of the data disclosed. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark details.