Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 16093
  • 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

rodCreateRect taking too long

thomas1000

Using the profiler and also just putting print statements in I found that I am having trouble with rodCreateRect taking longer and longer to process.  I have some very simple code:

for(i 0 Nx

   for(j 0 Ny

      <compute X & Y>

      rodCreateRect(?cvId Cv ?layer LPP ?bBox <Computed from X and Y by a simple linear formula>)

   );End for j

);End for i

This is such a simple code segment but when you have 700 or 800 rectangles to place on each inner loop, things are slowing down to the point that it takes hours to get throught this.  I realize that every time you create an object it has to add it to a large data structure, but is there no way to do this?  I cannot use the array or mosaic functions because the array is not cartesian.

Anyone have any ideas about how to speed this up?

Parents

  • Thanks Andrew for your response.  I have a of comment to your response that I believe makes my situation more difficult:

    1)  I wasn't clear enough in my write-up.  I am not just placing 800-900 rectangles - it is that number squared and it is being done for 7 layers.  Nx and Ny are both 800-900.  At first things go pretty fast until you get a ways into the placement on each layer but all along it is slowing down until it is litterally seconds between rectangles.  Seven layers worth of placement (same code run over seven times) took about 24 hours with only a small number of pre-existing shapes in the layout to define borders).  With seven complete iterations of this code, the total number of rectangles placed is, therefore, between 4.48 and 5.67 million - not 800 or 900.

    2)  I ran the profiler on the entire code and eliminated the other portions.  rodCreateRect seems to call an internal rodiCreateRect that is the bottleneck.  It uses the most time and memory.

    Even with 4.48 - 5.67 million elements it is hard to believe that things slow down that much.  Do you think the dbCreateRect operation would be faster?  Are there any other options available if I cannot simply use a mosaic?

Reply

  • Thanks Andrew for your response.  I have a of comment to your response that I believe makes my situation more difficult:

    1)  I wasn't clear enough in my write-up.  I am not just placing 800-900 rectangles - it is that number squared and it is being done for 7 layers.  Nx and Ny are both 800-900.  At first things go pretty fast until you get a ways into the placement on each layer but all along it is slowing down until it is litterally seconds between rectangles.  Seven layers worth of placement (same code run over seven times) took about 24 hours with only a small number of pre-existing shapes in the layout to define borders).  With seven complete iterations of this code, the total number of rectangles placed is, therefore, between 4.48 and 5.67 million - not 800 or 900.

    2)  I ran the profiler on the entire code and eliminated the other portions.  rodCreateRect seems to call an internal rodiCreateRect that is the bottleneck.  It uses the most time and memory.

    Even with 4.48 - 5.67 million elements it is hard to believe that things slow down that much.  Do you think the dbCreateRect operation would be faster?  Are there any other options available if I cannot simply use a mosaic?

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.