Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations KootK on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

ANSYS HELP! MEMORY ERROR

Status
Not open for further replies.

MarceloM

Mechanical
Sep 10, 2018
53
Hello,

I'm doing an foot pressure analysis with a insole and a suport (see picture pls).

The border conditions are very simple :
Top of tibia fibula and soft tissues = X=Y=Z=XR=YR=ZR=0
SUPORT= X=Y=XR=YR=ZR=0 Z=0,0004.

I have the following error:

*** ERROR *** CP = 156.875 TIME= 17:36:34
There is not enough memory for the Distributed Sparse Matrix Solver to
proceed. This is likely due to the use of pivoting while factoring
the matrix. Please increase the virtual memory on your system and/or
increase the work space memory and rerun the solver. Alternatively,
using the DSPOPTION command to switch to a different memory mode
and/or to specify additional memory for the solver may also help. The
memory currently allocated for the Distributed Sparse Matrix Solver
solver = 203 MB.

THANK YOU SO MUCH!!!

MORE INFORMATION:
FOR POSSIBLE RESUME FROM THIS POINT
THERE IS TOO MUCH PENETRATION AT 2222 CONTACT POINTS OF THE 3D CONTACT ELEMENTS
FORCE CONVERGENCE VALUE = 0.7870E+06 CRITERION= 0.5102E-04
VOLUME CONVERGENCE VALUE = 0.000 CRITERION= 0.1020E-05

DISTRIBUTED SPARSE MATRIX DIRECT SOLVER.
Number of equations = 214684, Maximum wavefront = 1729

*** NOTE *** CP = 127.203 TIME= 17:36:04
The initial memory allocation (-m) has been exceeded.
Supplemental memory allocations are being used.

Local memory allocated for solver = 687.594 MB
Local memory required for in-core solution = 483.191 MB
Local memory required for out-of-core solution = 200.383 MB

Total memory allocated for solver = 2786.367 MB
Total memory required for in-core solution = 1934.501 MB
Total memory required for out-of-core solution = 765.430 MB

*** NOTE *** CP = 127.844 TIME= 17:36:04
The Distributed Sparse Matrix Solver is currently running in the
in-core memory mode. This memory mode uses the most amount of memory
in order to avoid using the hard drive as much as possible, which most
often results in the fastest solution time. This mode is recommended
if enough physical memory is present to accommodate all of the solver
data.

*** WARNING *** CP = 127.844 TIME= 17:36:04
Pivoting has been activated for the Distributed Sparse Matrix Solver .
The memory required may greatly exceed the predicted amount. In that
event, use the DSPOPTION command to change the memory mode and/or
memory size used by the Distributed Sparse Matrix Solver.
curEqn= 39619 totEqn= 52966 Job CP sec= 132.734
Factor Done= 50% Factor Wall sec= 4.373 rate= 9224.3 Mflops

*** WARNING *** CP = 141.156 TIME= 17:36:18
There is not enough memory for the Distributed Sparse Matrix Solver to
proceed in the in-core memory mode. The Distributed Sparse Matrix
Solver will now restart using the out-of-core memory mode.

Local memory allocated for solver = 273.905 MB
Local memory required for in-core solution = 471.939 MB
Local memory required for out-of-core solution = 173.117 MB

Total memory allocated for solver = 1026.165 MB
Total memory required for in-core solution = 1816.210 MB
Total memory required for out-of-core solution = 556.887 MB

*** WARNING *** CP = 142.172 TIME= 17:36:19
The Distributed Sparse Matrix Solver is currently running in the
out-of-core memory mode. This memory mode may provide significantly
worse performance compared to the in-core memory mode, depending on
the amount of available system memory and I/O speed. Please monitor
the solver performance to ensure that the large amount of I/O to the
solver files does not create a bottleneck for performance.

*** WARNING *** CP = 142.172 TIME= 17:36:19
Pivoting has been activated for the Distributed Sparse Matrix Solver .
The memory required may greatly exceed the predicted amount. In that
event, use the DSPOPTION command to change the memory mode and/or
memory size used by the Distributed Sparse Matrix Solver.
curEqn= 44340 totEqn= 57705 Job CP sec= 156.797
Factor Done= 111% Factor Wall sec= 29.041 rate= 2692.6 Mflops

*** ERROR *** CP = 156.875 TIME= 17:36:34
There is not enough memory for the Distributed Sparse Matrix Solver to
proceed. This is likely due to the use of pivoting while factoring
the matrix. Please increase the virtual memory on your system and/or
increase the work space memory and rerun the solver. Alternatively,
using the DSPOPTION command to switch to a different memory mode
and/or to specify additional memory for the solver may also help. The
memory currently allocated for the Distributed Sparse Matrix Solver
solver = 203 MB.

Processor Model: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz

Compiler: Intel(R) FORTRAN Compiler Version 17.0.4
Intel(R) C/C++ Compiler Version 17.0.4
Intel(R) Math Kernel Library Version 2017

Number of machines requested : 1
Total number of cores available : 8
Number of physical cores available : 4
Number of processes requested : 4
Number of threads per process requested : 1
Total number of cores requested : 4 (Distributed Memory Parallel)

Latency time from master to core 1 = 2.041 microseconds
Latency time from master to core 2 = 2.061 microseconds
Latency time from master to core 3 = 2.172 microseconds

Communication speed from master to core 1 = 5823.39 MB/sec
Communication speed from master to core 2 = 5931.61 MB/sec
Communication speed from master to core 3 = 5570.48 MB/sec

Total CPU time for main thread : 154.7 seconds
Total CPU time summed for all threads : 157.6 seconds

Elapsed time spent pre-processing model (/PREP7) : 0.8 seconds
Elapsed time spent solution - preprocessing : 5.0 seconds
Elapsed time spent computing solution : 148.9 seconds
Elapsed time spent solution - postprocessing : 0.1 seconds
Elapsed time spent post-processing model (/POST1) : 0.0 seconds

Equation solver used : Sparse (symmetric)

Maximum total memory used : 3817.0 MB
Maximum total memory allocated : 7925.0 MB
Total physical memory available : 16 GB

Total amount of I/O written to disk : 1.5 GB
Total amount of I/O read from disk : 0.4 GB
 
 https://files.engineering.com/getfile.aspx?folder=a6c59aa4-1542-4e11-8d76-aad8f06b3e0b&file=xxx32.png
Replies continue below

Recommended for you

For Memory related issue, check following points.
-Revise/reduce the model size with coarse mesh/small no of elements/nodes and check whether it solves the problem
-Use Iterative/PCG solver in Analysis settings instead of direct/Sparse solver. Close all other applications which you are using Besides ANSYS in OS. Check your virtual memory available.
-Compress the node and element numbers before running by issuing command NUMMRG.
-Try to solve the problem on the machine with enough physical memory.
-Enforce in core solution by BCSOPTION Command if you have sufficient memory avaailable but ansys is going Out-of-core by default.
- Use following links for more information on memory allocation and error mitigation
Link 1
Link 2
Link 3
Link 4
Link 5
Link 6
 
Thank you for you awser.
I have -m 57000 -db 500. (MB)
I try the commands:
BCSOPTION,,INCORE
BCSOPTION,,OUTOFCORE
NUMMRG,node
NUMMRG,elem
NUMCMP,node
NUMCMP,elem
BCSOPTION,,INCORE,,,,performance
BCSOPTION,,INCORE,15,,,performance (15GB)
DSPOPTION,,INCORE,,,,performance
DSPOPTION,,INCORE,7,,,performance
I also try Direct with Full, modified and unsymetric and interactive.
I always have the same exact error.
I dont know what to do...
Thank you for the help.
 
Did you reduce your model size? 203 MB is relatively very small memory available for this type of complex analysis. Run your analysis on different machine/workstation with higher configuration.
Another thing, which contact algorithm have you used and what formulation of element is used. Referring this Link, if you use pure Lagrange contact and mixed u-P formulation, matrix pivoting will be enabled and which force the out-of-core solving for sparse solver.

Also check above link for the rough estimates of the memory requirements for different solver.

You can roughly estimate total no of DOF's of model by multiplying no of nodes by no of degrees of freedom per node.
 
I can't reduce my model size.
SOLID285 for bones, cartilage and soft tissues.
SOLID186 for insole and suport.
Contact between bone and cartilage is frictionless.
Contact between bone and soft tissues is bonded.
Contact between suport and insole is bonded.
Contact between insole and soft tissues is frictional 0.6 with augmented Lagrange nodal to target.

When i use SOLID187 instead of SOLID285 it works in core without problem, but how if i need 4x more memory?

Thank you.
 
MarceloM said:
When i use SOLID187 instead of SOLID285 it works in core without problem

You answered your query.

SOLID285 Assumptions and Restrictions-

The element is not computationally efficient when the model uses compressible material. In such cases, ANSYS, Inc. recommends using a more suitable (pure displacement) element such as SOLID185 or SOLID187.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor