I recall having performance problems in 5.1.41 when dealing with many flat shapes. I was able to get much better results after pre-allocating some memory to help eliminate garbage collection. If I recall correctly, I had to use needNCells on the dbobject. The following command will set aside enough memory to handle 4 million objects before garbage collection. You could also try increasing the number (but you'll need to stay within the memory limits of the tool). Use "top" to see how much memory your icfb or layout process is using before and after this command: needNCells('dbobject 4M) You can use gcsummary to see a list of all the object types and how many times garbage collection was run on that object in the last column. Another possibility is that dbProduceOverlap is more efficient in 5.1.41 than dbGetOverlaps. In 6.1.7, they appear about equal. The doc says this: Returns a list of all the shapes in a cellview whose bounding boxes overlap the area specified by l_bBox. This function interface is simpler than dbGetOverlaps if you are only interested in finding the overlapping shapes. Derek
↧