Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 16675
  • 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

Profiling the runtime of SystemVerilog Assertions

danlarkin

Hi all,

I'm concerned that a collection of assertion based checkers that I'm using are causing a dramatic slow down in the run time of my simulation. My hunch is that  the widespread use of multiple internal variables in some of the assertions are using vast amounts of memory and are thus negatively impacting the run time of the overall simulation.

How do I go about debugging such an issue? For example, I remember hearing that Incisive 8.2 was to have the ability to profile assertions - however when I tried out 8.20-p001 (and added the -profile option) I don't seem to be getting any additional profile information in the profile logfile?

 Any pointers o0r recommendations would be most appreciated.

Thanks

Daniel 

Parents

  • In addtion to what Chris showed, you will also get this information (copied from Assertion Checking in Simulation manual):

    In addition to the basic profiling improvements, which will be useful for diagnosing almost any performance problem, warnings will identify certain problems more specifically. These warnings will provide some indication as to why some assertions might be particularly slow, so that the user can improve them, including:

    • Large number of attempts in flight, indicating that the enabling condition might be too permissive, or that old attempts never completed
    • Large number of false starts, when an inactive property is activated, tests its data, and goes becomes inactive again
    • Continually increasing memory usage

    If profiling is enabled, these warnings are included in the simulation log file, once per affected assertion.
    These warnings also appear as part of the profile report, following the Assertion Summary section, so that they can be analyzed without the need to cross-reference the profile report against the simulation log file. 

    Tim

Reply

  • In addtion to what Chris showed, you will also get this information (copied from Assertion Checking in Simulation manual):

    In addition to the basic profiling improvements, which will be useful for diagnosing almost any performance problem, warnings will identify certain problems more specifically. These warnings will provide some indication as to why some assertions might be particularly slow, so that the user can improve them, including:

    • Large number of attempts in flight, indicating that the enabling condition might be too permissive, or that old attempts never completed
    • Large number of false starts, when an inactive property is activated, tests its data, and goes becomes inactive again
    • Continually increasing memory usage

    If profiling is enabled, these warnings are included in the simulation log file, once per affected assertion.
    These warnings also appear as part of the profile report, following the Assertion Summary section, so that they can be analyzed without the need to cross-reference the profile report against the simulation log file. 

    Tim

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.