• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Ocean parametric sweep fail due to memory

Stats

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

Ocean parametric sweep fail due to memory

Peter Madsen
Peter Madsen over 5 years ago

Hi All,

I am running an parametric sweep as a parametric set with a total of 9 sweep parameters. The total number of sweeps are 144

I am running a DC, SP and a two tone HB analysis.

After 122 sweeps the simulation crashes due to memory limitations as spectre alocates 27.9 GB on a 32 GB machine.

This is okay if the analysis needed that amount of RAM, but running the settings for the sweeps as a stand alone simulation uses less than 5 GB

It seems there is a bug in the parametricrun() command as simulation data never leaves memory.

Is there a way force the data out of memory between each run?

Another way of fixing this is to split up the sweep in smaller sweeps  in a for loop, but I would like to avoid this.

I am using spectre version 18.1.0.370.isr7 64-bit

Hope some can help,

Peter

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    I'm not sure why the memory should grow - you should contact customer support about that.

    I was thinking that you could just use: envSetVal("spectre.envOpts" "controlMode" 'string "batch")
    at the beginning of your OCEAN script, but with paramset it still runs a s a single invocation of spectre (conventional parametric analysis would invoke spectre separately for each run).

    You could use ADE XL or ADE Assembler instead. You define the individual variables as a list of the values you wish you sweep, and then select the variables in the list of global variables and use Right Mouse->Group as Parametric Set. If you do it this way, each simulation will be an individual run and so the memory should not accumulate.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Peter Madsen
    Peter Madsen over 5 years ago in reply to Andrew Beckett

    Hi Andrew

    Thanks for your suggestion with the env option. This didn't change the memory growth.

    So I have contacted cadence support.

    Thanks,

    Peter

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Peter Madsen
    Peter Madsen over 5 years ago in reply to Andrew Beckett

    Hi Andrew

    Thanks for your suggestion with the env option. This didn't change the memory growth.

    So I have contacted cadence support.

    Thanks,

    Peter

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information