• 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 Design
  3. Monte Carlo - RAM usage issue, run each point consecutively...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 2289
  • 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

Monte Carlo - RAM usage issue, run each point consecutively?

michael10
michael10 over 4 years ago

Hi,

I have the same question as this 10 year old post:
community.cadence.com/.../is-there-a-way-to-prevent-monte-carlo-runs-from-accumulating-ever-more-ram-space-memory

I try to run Monte-Carlo on a large circuit.
For example running 8 MC points with 4 jobs, each job has to run 2 points consecutively.

The issue is that the memory (RAM) seems to fill up. One simulation takes about ~150GB of RAM (which is OK, the system has 256GB).
After a job finishes the first point, I would expect it to clear the RAM, and continue with the second point with almost 0 RAM usage at the beginning.
But apparently the data from the finished point stays in the RAM, filling it up, and the simulation gets killed before the second point can finish.

Is it possible to start a new job for each Monte-Carlo Point, and running each point consecutively?

Informations:
- In the Job Policy Setup, Distribution method is set to "Command".
- Cadence Version is IC6.1.8-64b.500.8

  • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 4 years ago

    I suggest you take a look at the article How to force Monte Carlo to treat each simulation run individually

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Frank Wiedmann

    In addition, I would suggest that you speak to customer support. For a start, that seems like an excessive memory consumption - there may be things that can be done to reduce that, and also I would not expect the memory to accumulate like this either.

    If you had been using a later version, then you would have been able to pick the "LSCS" option (as opposed to "ICRP") on the Job Options form which is a newer way of handling the resources (still distributed) which avoids having a large virtuoso launched for each simulation, and has some more robust handling of the messages (mainly beneficial when you have a lot of parallel simulations, but it's now the default in current versions). When you enable LSCS, a new option appears on the Monte Carlo advanced options so that you can limit the maximum points per job to be a particular number (e.g. 1):

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • michael10
    michael10 over 4 years ago in reply to Andrew Beckett

    Thank you, I'll have a look at both options!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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