Stats

  • Locked Locked
  • Replies 12
  • Subscribers 150
  • Views 19545
  • 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

time delay in simple program

bloodwayn

Hi,

i have a little time problem. i've wrote a program which creates in an area a specific numbers of rectangles ... so it begins in the left buttom corner, creates rectangles on the buttom to the right until the end of the area(with a while loop). after this, with an other while loop i jump up one line. in this line the first while loop makes his work again. and so on until the area is full of rectangles.
so this works in principle. but when the procedure jump in the second line it starts to become extremly slowley. and it doesn't matter how many rectangles are created.

so i can't understand why it becomes so slowely when the program starts the same procedure for a second time.

regards
Philip

p.s.: this is only a short extract out of my program. so in the same time where a rectangle will be created, it creates a new cellview which will be opened an closed again.

Parents
  • Andrew Beckett

    If it's time you're worried about, you might be better off profiling time rather than memory.  Also make sure that you start the "run" button just before you invoke your SKILL code (try to remove the effect of anything else in the system), and hit the "stop" button right after it completing. Make sure you hit "reset" before runs.

    You can also through the UI show the critical path - this can help in prioritizing it. 

    From what you've shown, it appears that most of the memory is being used in  various Cadence functions:

    drFindPacket                       1067120  1067120
    leGetValidLayerList                1034640  1034640
    hiMakeLPChoiceList                  866000   866000
    hiDisplayWindow                     788144   788144

    However, it's pretty much impossible to tell you what to improve without seeing the code! We have no idea what your code is doing.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    If it's time you're worried about, you might be better off profiling time rather than memory.  Also make sure that you start the "run" button just before you invoke your SKILL code (try to remove the effect of anything else in the system), and hit the "stop" button right after it completing. Make sure you hit "reset" before runs.

    You can also through the UI show the critical path - this can help in prioritizing it. 

    From what you've shown, it appears that most of the memory is being used in  various Cadence functions:

    drFindPacket                       1067120  1067120
    leGetValidLayerList                1034640  1034640
    hiMakeLPChoiceList                  866000   866000
    hiDisplayWindow                     788144   788144

    However, it's pretty much impossible to tell you what to improve without seeing the code! We have no idea what your code is doing.

    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.