Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13867
  • 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

ipcBeginProcess() appear to slow down script execution

Flaxter

Hi there,
 I am having a "speed" issue using ipcBeginProcess() command while trying to execute Calibre DRC on given layout. The code I am using is:

CommandLine="calibre -drc -hier _myDrcSetup_"
ipcP=ipcBeginProcess(CommandLine) ipcWait(ipcP)

,which gets the job done (approximately 25mins). However, using Calibre GUI or that command sh("calibre -drc -hier _myDrcSetup_") the task is complete in far less time (~9mins).  Calibre set up is all the same in all three cases, am preforming DRC on same layout etc. With ipcBeginProcess Calibre output files are "written" slower and it doesn't seem like it gets the job done and process just "hangs" for a given period of time.
The only reason and I am not using sh() is that Calibre task is not done if parent linux terminal is accidentally closed and also I am afraid it might mess up the script flow. ipcBeginProcess()+ipcWait() seems more civil way to solve the problem.However, such slow execution is not applicable.

  • I can't see a good reason for this. So please contact customer support. One thing you might want to try is redirecting the stdout of calibre if it is producing a lot of output data:

    CommandLine="calibre -drc -hier _myDrcSetup_ > ./myCalibre.log"

    See if that helps? Since with IPC it allows you to read the results with ipcReadProcess(), you may be flooding the input buffer if there's a lot of stdout from the child process. If you're not using that output, redirecting to a log file may make more sense. Or alternatively use:

    CommandLine="calibre -drc -hier _myDrcSetup"
    ipcP=ipcBatchProcess(CommandLine "" "./myCalibre.log")
    ipcWait(ipcP)

    Regards,

    Andrew.

  • Hi Andrew, both of this solutions worked properly. Thanks for helping out.

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.