Trouble with memory for 3D soil model

[MIRomero]

I am trying to run a dynamic analysis for a 3D soil model using Bbarbrick elements with 31668 elements and 35046 nodes in OpenSees 2.4, do you think it is necessary to use parallel processing for this problem?

I have run successfully a column of soil with the same soil and analysis properties for many input motions, but now that I expanded the model, it is not running. What is the maximum capacity that OpenSees has to work properly without Parallel Processing?

Thank you in advance for your answer.

[fmk]

There is no hard limit. The program runs out of memory when it runs out of memory. The windows version is only 32bit, and runs out of memory faster than a typical linux build (e.g. that on NEEShub) which are 64bit. Make sure you are using a sparse solver, these typically use require less memory. If this is still a problem you will have to try the SP parallel version, just remember to change the system to Mumps when you do.

[MIRomero]

Thank you for the answer. I am indeed using sparse solver.
I left the model running in NEESHub, and it was running slowly, but running. The next day when I logged in to my session, the OpenSees Interpreter was frozen, meaning the the screen was grey. I opened again the OpenSees Interpreter from the application tab within the same session, and I got back the Interpreter but none of the script from the day before was shown. I left the model re-running in NEESHub, and it got frozen again.

I am getting this filexfer469.log:

started on Thu Jan 17 11:56:58 EST 2013
listening on port 9037
accepted client sock2 on 127.0.0.1
REQUEST: IMPORT /tmp/upload467.html ABSOxf6Ln2oaiSz5 FILEXFER/1.0
accepted client sock3 on 128.46.19.185
REQUEST: GET /download/upload467.html?token=DnQHpNIvlJHvSUCKjulR HTTP/1.1
disconnected client sock3
accepted client sock3 on 128.46.19.185
REQUEST: POST /upload HTTP/1.1
disconnected client sock2
disconnected client sock3
cleaned up DnQHpNIvlJHvSUCKjulR
inactive for a while -- shutting down...

I am not sure what is the cause of disconnection.

Anyhow I will try now with OpenSeesSP and mumps solver.

Thank you for your advice.

[fmk]

just a note when using the workspace and the parallel versions. you have to run it using mpi

/apps/neesutils/mpich2/bin/mpirun -n 1 /apps/share64/opensees/local/bin/OpenSeesSP main.tcl