• 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. How to speed up plot with big result

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 6428
  • 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

How to speed up plot with big result

sjwprcker
sjwprcker over 2 years ago

Hi,

My sim result (Interactive.x) is ~ 300G. When I try to plot one signal in viva, it takes me > 1hour to load, which is too slow. I am wondering is there anyway to plot a specific signal quicker? It seems viva try to load full result (300G) and show the one I need to plot. 

Thanks for your help!

  • Cancel
  • ShawnLogan
    ShawnLogan over 2 years ago

    Dear sjwprcker,

    sjwprcker said:
    My sim result (Interactive.x) is ~ 300G. When I try to plot one signal in viva, it takes me > 1hour to load, which is too slow

    My experience with large databases (approaching 1 TB) suggest an hour is pretty good!  It is not unusual to have to wait many hours to both access and post-process large simulation result databases. I can only suggest what I have done in the past to try to minimize the time. These are my personal suggestions only.

    1. Reduce the number of saved outputs to as small a set as possible

    a. If using an extracted view based netlist, make sure you are not saving all fractured nets of a specific schematic node

    2. Use the strobepoint feature and only save the strobed timepoints

    3. Place all your post-processing and plotting commands in an ocean script to enable background processing and allow them to run while you perform other tasks.

    4. Make sure your results database is on the same network (i.e. reduce access time)

    5. If you have N outputs, sort them into, say, M groups (M1, M2, M3...). Run the same simulation M times where each simulation has one of the sets of Mi outputs. Although you are running the same simulation M times, your database size will be reduced by a factor of M and hence will expedite your plotting times.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to ShawnLogan

    Just knowing the overall size of the database is not enough too - is this transient data? Are you using PSF XL output format? Which IC and spectre versions are you using? 

    I would strongly advise contacting customer support - I wouldn't in general expect it to be that slow, but having some idea of the nature of the database (are there lots of points, or lots of signals, or lots of separate databases over sweeps/corners etc) would help get a better understanding of where the bottleneck lies. That's not something that's particulary feasible to do on the forums.

    Andrew

    • 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