Optimizing iLogic rule performance

[TommySWE]

I have a rule that controls a multi-solid body part with a lot of suppressions, forcing of values by if statements and so on.

The rule as of now is quite heavy to run, takes about 20-30 seconds if you make a lot of changes in the form that I use to control the part.

Are there any guidelines for how to write code in order to optimize the performance of my iLogic rule?

[wimann]

Ummmm... I know of nothing that isn't already obviuos.

Familiarize yourself with ways to simplify IfThen's so that they can run smoother?

Familiarize yourself with alternatives to IfThen's that may be easier for the machine to run?

That's all I got. I'll be interested to see what others say.

[john.grimshaw]

I'd look at select case statements if applicable, it helped me massively when I had iParts/iAssemblies that had to be selected based on inputs. it improved the speed of the update from about 15 minutes to 90 seconds.

[frederic.vandenplas]

I would personnaly uncheck the immediate  Update in the parameter dialog box (through code) or manual for starting.

Or you can move the end of part before the first sketch, at the end move it to the end of your tree if you are altering parameters

or features.

Without code from your side, these are the most obvious things to do.

I would be helpfull for us and for you if you post your code to examine the stuff you do.