Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 14303
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

running multiple ocean simulations from a single host

Wonyoung

Hello,

I had problems running multiple ocean simulations from a single host under IC5.1.4. Several of the simulations would crash, but the problem was solved by running only 1 ocean simulation per host. (related post: www.cadence.com/.../18294.aspx).

I tried this with IC6 to see if that changes anything. We have a variety of hosts with 4-12 cores each, and I ran 1 ocean simulation per core (4-12 simulations per host). I used the same command "ocean -log CDS.log.mylogfile -nograph -restore myoceanfile.ocn", and used different log file and .ocn file names across simulations. The ocean simulations crashed again, but with a slightly different message (attached below). Again, the problem didn't appear when I ran only 1 simulation per host.

Could anyone help me solve this problem and let me run multiple ocean simulations per host? It just doesn't seem right that I can run only 1 ocean simulation per host when there's a ton of multi-core hosts out there.

Thank you very much.

X connection to vasuki.eecs.harvard.edu:80.0 host broken (explicit kill or server shutdown)
\e IO Error 32 (Broken pipe) on Display "vasuki.eecs.harvard.edu:80.0"
\e Aborting due to fatal X IO error.
\o INFO (DB-170018): (dbPanic) dumping stack
\o virtuoso:dbPanic+197()
\o libvirtuos_sh.so:voDoAbortFuncs+37()
\o libvirtuos_sh.so:voSigAbort+167()
\o :__kernel_sigreturn+0()
\o libc.so.6:abort+257()
\o virtuoso:gliXIOErrorHandler+325()
\o libX11.so.6:_XIOError+45()
\o libX11.so.6:libm.so.6/PLT+2159027()
\o libX11.so.6:XFlush+49()
\o virtuoso:_Z12hiiSetCursorm+277()
\o virtuoso:hiiDiceCursor+47()
\o virtuoso:hiGetUserAbort+158()
\o libvirtuos_sh.so:voGetUserAbort+34()
\o libcdsIlIpc_sh.so:ipcxSleep+175()
\o libil_sh.so:iliVcodeEval2+21063()
\o libil_sh.so:ilxSkillEval2+216()
\o libil_sh.so:iliLoadPort+1431()
\o libil_sh.so:iliVcodeEval2+26932()
\o libil_sh.so:ilxSkillEval2+216()
\o libil_sh.so:iliEvalString+611()
\o libil_sh.so:_ilErrSetString+235()
\o libil_sh.so:ilErrSetString2+60()
\o virtuoso:hiMainLoop+404()
\o virtuoso:_ZN3rde15startHiMainLoopEv+2619()
\o virtuoso:Tcl_Main+781()
\o virtuoso:_ZN17TclCommandAdaptor8mainLoopEiPPcPKcRKSt6vectorI9ctuStringSaIS5_EEPFvvE+591()
\o virtuoso:_Z11finaleEntryiPPcPKcbP16finaleAppHarness+3885()
\o virtuoso:_Z12rdeStartMainiPPc+61()
\o virtuoso:main+997()
\o virtuoso has encountered a fatal internal application error and will now exit.
\o A crash report file for this error can be found at: /tmp/crashReport_031511_1758_IC6.1.4.500.1_wonyoung_vasuki.eecs.harvard.edu.log

Parents
  • We can recommend to customers to use a grid computing solution to dispatch their ocean/runams jobs on different hosts. In my case, I introduced LSF calls into my simplan to randomize the hosts, and it solved my problem by greatly reducing the likelihood of contention.
Reply
  • We can recommend to customers to use a grid computing solution to dispatch their ocean/runams jobs on different hosts. In my case, I introduced LSF calls into my simplan to randomize the hosts, and it solved my problem by greatly reducing the likelihood of contention.
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.