Hi Frank,
We have compiled OpenSees in Linux Redhat Enterprise Ed. on 3 GHz, 64-bit processors. It compiles fine, however runs very slow (i.e. 4 times slower than in a 2 GHz, 32-bit Win32 machine). We suspect the Linux version may be a DEBUG version, however the DEBUG_FLAG in Makefile.def appears to be undefined.
Do you have any thoughts on how to optimize the Linux version so that it runs faster?
Thanks!!!! We appreciate your help.
Kathryn & Pedro
Search found 3 matches
- Mon Jan 09, 2006 6:03 pm
- Forum: Framework
- Topic: Compiler Optimizations in Linux Redhat Enterprise
- Replies: 3
- Views: 6086
- Thu Aug 04, 2005 2:41 pm
- Forum: Framework
- Topic: Calculation Times in 1.5.2 vs 1.6.2
- Replies: 3
- Views: 6081
mistake!
Please disregard my earlier posting.
I had the compiler settings wrong in visual studio.NET and was compiling the debug version instead of the release version. The release version for 1.6.2 has similar calculation times to that of 1.5.2 for the example problem I referred to.
Sorry for the confusion. I hope others wont make the same mistake in the future.
I had the compiler settings wrong in visual studio.NET and was compiling the debug version instead of the release version. The release version for 1.6.2 has similar calculation times to that of 1.5.2 for the example problem I referred to.
Sorry for the confusion. I hope others wont make the same mistake in the future.
- Wed Aug 03, 2005 1:57 pm
- Forum: Framework
- Topic: Calculation Times in 1.5.2 vs 1.6.2
- Replies: 3
- Views: 6081
Calculation Times in 1.5.2 vs 1.6.2
I recently upgraded from OpenSees 1.5.2 to v1.6.2 (cvs) and have noted significantly longer calculation times for the new version of the code. I made a simple 3D test model of a cube meshed with 1000 std brick elements. The ElasticIsotropic material was used and a single point load was applied over 10 calculation steps (Newton algorithm and BandGeneral solver was used because of interest for other models). Under version 1.5.2, this simple elastic model took 67 seconds on my machine. Under version 1.6.2, the model calculation took 477 seconds. The results and convergence behavior are identical for the two versions; however the calculation time is extremely different (7 times longer!).
Have others noticed the longer calculation times with v1.6.2 or have an idea why this is occurring?
Have others noticed the longer calculation times with v1.6.2 or have an idea why this is occurring?