Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14236
  • 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

Parallelizing simulation with a variable sweep in an analysis itself

Emiel

Hi,

I'm using virtuoso ICADVM18.1-64b.83 and spectre 18.1.0.077.

I've set the max. jobs, in the Job-setup relatively high (28).

I've set the High-Performance Simulation Options to APS and multi-threading with manual the number of threads equal to 28 as well.

The number of available tokens is not limiting.

When sweeping a design variable in Meastro (in the Data View), the number of created jobs and thread usage is as expected.

However, when instead of sweeping a design variable in the Data View, sweeping it only in the Analysis (qpss) itself, only a single job is created and a single thread is used. How can ensure/allow that a sweep in the analysis itself is parallelized as well during simulation?

When only a single tests/analysis is ran, a window with spectre.out pops up. This doesn't pop up when there are multiple tests/analysis, is there a way to still (live) see the spectre.out for a specific analysis during a simulation with multiple tests/analysis?

Regards,

Emiel

Parents
  • Andrew Beckett

    Hi Emiel,

    If you sweep within the simulator, it doesn't run the sweep points in parallel. Particularly with the RF analysis, there's a lot of shared information that is needed across those sweeps and so it wouldn't be trivial to run those points in parallel (without the memory consumption increasing a lot in many cases) - so right now that is not supported. You do have multi-threading which will mean that some of the work of each sweep point can be done in parallel, but it's not as simple as considering each sweep point in parallel. With that, i would say specifying 28 threads is pretty high - it's unlikely you'll really be utilising that many threads. I don't see why you specified them both as 28 - that seems a bit odd to me.

    If you are running in ADE XL/Explorer/Assembler and there are multiple jobs running, the spectre.out is not displayed (because there would be lots of them, and potentially thousands of windows could end up being displayed). However, you can go over one of the points in your ADE Results table and use the context (Right Mouse Button) menu to display the output log for that specific simulation point.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Hi Emiel,

    If you sweep within the simulator, it doesn't run the sweep points in parallel. Particularly with the RF analysis, there's a lot of shared information that is needed across those sweeps and so it wouldn't be trivial to run those points in parallel (without the memory consumption increasing a lot in many cases) - so right now that is not supported. You do have multi-threading which will mean that some of the work of each sweep point can be done in parallel, but it's not as simple as considering each sweep point in parallel. With that, i would say specifying 28 threads is pretty high - it's unlikely you'll really be utilising that many threads. I don't see why you specified them both as 28 - that seems a bit odd to me.

    If you are running in ADE XL/Explorer/Assembler and there are multiple jobs running, the spectre.out is not displayed (because there would be lots of them, and potentially thousands of windows could end up being displayed). However, you can go over one of the points in your ADE Results table and use the context (Right Mouse Button) menu to display the output log for that specific simulation point.

    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.