Out of curiosity, can too much boolean in your code slow down your app?

Dell7730

is there such thing as too much stack of rules within one actor?

Socks

@dellagarpo said:
how much is too many rules? lol

One more than is needed for efficient implementation of the actor's functionality.

tatiang

@dellagarpo said:
how much is too many rules? lol

Sometimes one rule is too many. Sometimes 20 rules are just fine. It all depends on things like Constrain Attribute behaviors, Timers, Loops, etc. There's no set number that indicates a problem.

tatiang

Too much boolean? No. Too many rules? Yes.

Dell7730

@tatiang said:
Too much boolean? No. Too many rules? Yes.

how much is too many rules? lol

Dell7730

@Socks said:
One more than is needed for efficient implementation of the actor's functionality.

Dang It, lol

mhedges

I've read in some threads that "constrain attribute" is more likely to affect performance; I haven't come up on booleans doing that.

Dell7730

@mhedges said:
I've read in some threads that "constrain attribute" is more likely to affect performance; I haven't come up on booleans doing that.

it does, once i reduced it to a max of 3, it went smooth sailing after.