Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13339
  • 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

Destroying structures

Atul Dwivedi

Hi there,

I came across defstrct and was amazed at the capability it gives. I make many structures and store them in a list and do some sorting etc. ex:

struct1=make_myStrcut(..)

struct2=make_myStrcut(..)

myStructList=('struct1 'struct2..)

In logic everything is working fine and as expected. However, I need to do this task many times, and everytime I am making new structures and storing this in this list, without destroying the previous instances.

myStructList=('newStruct1 'newStruct2..) 

This clogs up the memory (RAM + swap) in the server as the previous 'struct1s are not 'destroyed'. Is there a simple function to clean up these structures.

Note: The no. of structures are many (with considerable data).

I had a quick look in the forum and manual, but could not come up with anything close.

Any help would be appreciated.

Thanks and Regards,

Atul 

Parents
  • Andrew Beckett

    Atul,

    SKILL uses garbage collection to manage memory. The way that this works is that if a data structure is no longer referenced, it is available to be garbage collected. For each type, SKILL maintains a pool of free objects, and as a program requests more it will allocate them from this free pool. When that pool is empty, a garbage collection is triggered and it will reclaim any unreferenced objects and add these to the free pool. If nothing is spare after garbage collection it will allocate more memory.

    In your case, setting myStructList to nil or removing the entries from the list that you no longer require would have the effect of making the Structure instances garbage (assuming that they are not referenced elsewhere).

    Regards,

    Andrew 

Reply
  • Andrew Beckett

    Atul,

    SKILL uses garbage collection to manage memory. The way that this works is that if a data structure is no longer referenced, it is available to be garbage collected. For each type, SKILL maintains a pool of free objects, and as a program requests more it will allocate them from this free pool. When that pool is empty, a garbage collection is triggered and it will reclaim any unreferenced objects and add these to the free pool. If nothing is spare after garbage collection it will allocate more memory.

    In your case, setting myStructList to nil or removing the entries from the list that you no longer require would have the effect of making the Structure instances garbage (assuming that they are not referenced elsewhere).

    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.