Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 13844
  • 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

Long script runs out of memory

thomas1000

I have a SKILL script that runs out of memory and terminates Cadence when running on a medium-sized MMIC.  I will try assigning intermediate variables to nil after they are used but is there anything I can do either to increase memory or in general to redue its use?

Parents

  • Do you have a Skill development license? If so, you can profile the performance and memory usage of your program:

    CIW->Tools->Skill Development
    Click on Skill Profiler
    From the profile menu, you can choose "Start Profiling Time" or "Start Profiling Memory".
    After the profiler has started, run your program. Since it is currently crashing Cadence, you'll want to run a smaller data set, or even ctrl-c to cancel the command before you crash.
    When your run has finished, press the "Stop" button on the profiler form (the square) and you'll see some information about the top memory users or time users.
    Press the Browse button (looks like a tree) and it will build a tree of your code to help you see your memory usage in your code hierarchy.
    Then examine the profile results to help pin point your memory hog. If you are able to get this far and isolate the problem code, then post it and we can help you improve it.

    If you don't have the profiler, you might want to post a sample of your code.

    Derek

Reply

  • Do you have a Skill development license? If so, you can profile the performance and memory usage of your program:

    CIW->Tools->Skill Development
    Click on Skill Profiler
    From the profile menu, you can choose "Start Profiling Time" or "Start Profiling Memory".
    After the profiler has started, run your program. Since it is currently crashing Cadence, you'll want to run a smaller data set, or even ctrl-c to cancel the command before you crash.
    When your run has finished, press the "Stop" button on the profiler form (the square) and you'll see some information about the top memory users or time users.
    Press the Browse button (looks like a tree) and it will build a tree of your code to help you see your memory usage in your code hierarchy.
    Then examine the profile results to help pin point your memory hog. If you are able to get this far and isolate the problem code, then post it and we can help you improve it.

    If you don't have the profiler, you might want to post a sample of your code.

    Derek

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.