Stats

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

  • Hi Vivek,

    First of all, I'd suggest you take a look at Cadence Online Support Solution 11495216. This describes how to optimize the speed of startup of the background process.

    The reason a background process is created is for several reasons:

    1. To netlist the design
    2. To launch the simulation
    3. To do the results post-processing.

    It might seem like overkill to do this, but the primary reason is that if you are running multiple simulations in parallel (e.g. over a sweep, or corners), you can launch several of these - and they can be distributed on a compute farm (e.g. using LSF). That means that the netlisting and post-processing are not a bottleneck by being done in the foreground process. 

    Also, the background process should start up pretty quickly (say, within 10 seconds, if set up properly), and ADE XL will also re-use it for subsequent runs that are done within  the "linger time" (see solution 11575172) - so you don't have to pay this 10 second overhead again and again.

    It also does not use additional ADE XL licenses for the background processes (so it is not a money making scam!).

    Hope that's clear,

    Regards,

    Andrew.

Reply

  • Hi Vivek,

    First of all, I'd suggest you take a look at Cadence Online Support Solution 11495216. This describes how to optimize the speed of startup of the background process.

    The reason a background process is created is for several reasons:

    1. To netlist the design
    2. To launch the simulation
    3. To do the results post-processing.

    It might seem like overkill to do this, but the primary reason is that if you are running multiple simulations in parallel (e.g. over a sweep, or corners), you can launch several of these - and they can be distributed on a compute farm (e.g. using LSF). That means that the netlisting and post-processing are not a bottleneck by being done in the foreground process. 

    Also, the background process should start up pretty quickly (say, within 10 seconds, if set up properly), and ADE XL will also re-use it for subsequent runs that are done within  the "linger time" (see solution 11575172) - so you don't have to pay this 10 second overhead again and again.

    It also does not use additional ADE XL licenses for the background processes (so it is not a money making scam!).

    Hope that's clear,

    Regards,

    Andrew.

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.