The OpenSees Community

I do not mean the symspare solver is bad. On the contrary, the symspare solver in my test is better than the profileSPD. What I question is the integration of solvers in OpenSees. It uses lots of buffer and uses up the memory, not the nonzero.

Number of nonzero entries in the matrix for different method is shown. Though the number of nonzero entries in symsparse solver is fewer, the memory consumption is even larger than profileSPD due to the integration of fortran, c. It causes poor memory management.

Node num Element num equnum None zero system ProfileSPD numberer Plain 30000 36421 108900 43180731 system ProfileSPD numberer RCM 30000 36421 108900 44036667 system SpareSPD nested dissection ordering 30000 36421 108900 9803302 system SpareSPD minimum degree ordering 30000 36421 108900 5719914(fewes...

I wrote a simple test below: wipe ; model basic -ndm 3 -ndf 3 set Econ [expr 2.55*1e10 ] nDMaterial ElasticIsotropic 1 $Econ 0.25 1.27 set eleArgs "1" set element stdBrick set nx 10 set ny 10 set nz 300 set eleNum [expr $nx*$ny*$nz] set nn [expr ($nz+1)*($nx+1)*($ny+1) ] block3D $nx $ny $n...

I can't download now either