time delay in simple program

 I suspect that you may be creating enough data in memory that the garbage collection is triggered. This refers to the SKILL data and not to the database data. The garbage collector is triggered to clean up unused variables which you have created.

Turn on the profiler and run your program and you will see what parts are taking the most time. gc is the garbage collector. If you are building large lists of information using cons or append, you may want to use a command like tconc which modifies the list in place.

Ted

Hey Ted

thanks for your reply. and exactly i've also thought about, if i have understood you correctly. ;)
but how can i turn on the profiler ^^

and is there an other possebility to increase the memory or to decrease the data?

regards
philip

 The profiler is part of the SKILL development environment. It is found under the Tools menu in the CIW. There is some good documentation on it in the help files.

 Without seeing the code, I cannot tell you how to modify it. You may be able to do things in the database (use arrayed instances) or in the code itself (mapcar). That will be determined by exactly what you need the program to do.

Ted

thanks ... i've found it.

here is the list which was created by the SKILL-Profiler. So i can see  how many memory are necassary for each function. but what conclusion can i draw out of it. Can you say me anything more?

Regards
philip

thanks ... i've found it.

here is the list which was created by the SKILL-Profiler. So i can see  how many memory are necassary for each function. but what conclusion can i draw out of it. Can you say me anything more?

Regards
philip

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.

I agree with Andrew. The time profiling is a lot more telling. Looking at the amount of memory used by commands like "drFindPacket", "leSetLayerValid", "techGetSpacingRule" and "leGetValidLayerList", it would seem like you are calling these commands more than necessary. Running these commands once and storing off the values can save a lot of time.

Derek

 Derek and Andrew are correct, you want to look more at the time each command is using rather than the memory. The gc command is the garbage collector and that gets triggered when you free a large amount of data such as reinitializing variables.

In your command list you have a number of interactive commands, (leSetLayerValid, drFindPacket), are these part of your code? Be sure, as Andrew said, to profile only the code by starting and stopping around the execution of the procedure.

 Ted

 hi,

and first a happy new year at all.

i've saved the times. i hope you're able to make use of these data.

http://nopaste.info/c455c23d96.html

regards
philip

Hi Philip,

As I said, it's almost impossible to comment further without seeing the code.

Regards,

Andrew.