Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 17136
  • 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

Long startup for simulations using ADE-XL

vivkr

Hi,

 

I was wondering why my ADE-XL sims were taking so long to run, and looking through the log showed me that a new Cadence icfb session is being started for each single run! That does seem a bit well ($%#*&%*&) when all that is needed is a Spectre run.

Is there any way to get the tool to merely start Spectre runs rather than entire Cadence sessions? It can't be something meant to rack up more licenses since Spectre licenses (which are really needed) are anyway far more expensive.

Thanks,

Vivek 

Parents
  • vivkr

     Just for the record. I set the linger time to a large value and set the option to prevent .cdsinit from being loaded by each new ADE-XL job, and there is remarkable improvement in the speed now. As a matter of fact, the simulations start immediately in the later runs as the ADE-XL jobs are already running in the background.

    At present, this works only locally as distributed jobs are not always started on the same machine for successive runs. However, that's another issue.

    Sunil: I did try to set the default history entries to be larger than 3 but it doesn't seem to work. Anyway, I think I can lock previous runs and then they ought to be retained then as locked runs do not count towards the quota of 3 history entries.

     Vivek

Reply
  • vivkr

     Just for the record. I set the linger time to a large value and set the option to prevent .cdsinit from being loaded by each new ADE-XL job, and there is remarkable improvement in the speed now. As a matter of fact, the simulations start immediately in the later runs as the ADE-XL jobs are already running in the background.

    At present, this works only locally as distributed jobs are not always started on the same machine for successive runs. However, that's another issue.

    Sunil: I did try to set the default history entries to be larger than 3 but it doesn't seem to work. Anyway, I think I can lock previous runs and then they ought to be retained then as locked runs do not count towards the quota of 3 history entries.

     Vivek

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.