Keep getting "insufficient memory" error in workbench 11

[mbwittig]

I keep getting "insufficient memory" error in workbench 11 when running a simulation. However, I was watching the memory usage with task manager and it doesn't appear that I am actually using all the physical memory when I get that error, let alone any virtual memory. I thought Ansys Workbench manages memory automatically? Has anyone encountered this error?

 

[cbrn]

Hi,
yes, it may be that Ansys' request for a CONTIGUOUS memory block could not be fulfilled by the Operating System.
In this case there is very little you can do. For example, remove from memory all the Windows services which are not strictly required. Remove any unuseful driver or whatsoever. IF possible, stop the antivirus from running.

Regards

 

[mbwittig]

I see this in the solution information:
***** ANSYS COMMAND LINE ARGUMENTS *****
BATCH MODE REQUESTED = NOLIST
2 PARALLEL CPUS REQUESTED
MEMORY REQUESTED (MB) = 550
START-UP FILE MODE = NOREAD
STOP FILE MODE = NOREAD
DATABASE SIZE REQUESTED (MB) = 500


Why is the memory requested / database size requested only 500 mb each when the PC has 3 GB installed?

Is there a way of manually setting the command line memory when using a Workbench magnetostatics sim?

Thanks for any help!

 

[Stringmaker]

This should be an easy fix. I don't have WB up in front of me but I think if you go to Tools > Variable Manager and enter the following variables:

AMK MEMORY - value (in KB)
AMK DBMEMORY - value (in KB)

these function similarly to the -m and -db switches within Ansys. In your case I would try:

AMK MEMORY = 2048000
AMD DBMEMORY = 512000

You may be able to set the AMK DBMEMORY smaller if you don't have a huge database. Play around with these though. Good luck.

 

[cbrn]

Hi,
the database mem size seems too big in relation to the total workspace mem size.
If WB is not managing the mem requests correctly (strange...), then play with specifying a huge total workspace size (can not be, however, greater than the biggest CONTIGUOUS mem block allowed by your system, which is much less than the free mem in Win32 Operating Systems...) while forcing a small database size.
This, only for the solution phase.
If you still have problems, solve the job by submitting it in batch with the Ansys Launcher. In this way, you save the mem required to keep the Ansys' GUI on.

Regards

 

[yabande]

I got the same problem and changed workspace and database size memory as much as I could in every method describe above, but still got error.
finally I changed the mesh size and problem solved!!!

 

[cbrn]

Of course...
You'd better run solver diagnostics before concluding "a priori" that a solution database can be held in memory. It's not enough to look at the first memory estimates, such as those shown in a previous post, since those are output at a stage in which the system matrices have not been compiled yet.

Regards

 

[yabande]

Dear cbrn,

Could you explain it a little bit more, because I looked at "solve process setting" and memory setting is only option.