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

Dell7730Dell7730 Member, PRO Posts: 388
in Community Tutorials

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

Best Answers

  • SocksSocks London, UK.Posts: 12,822
    Accepted Answer

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

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

  • tatiangtatiang Posts: 11,949
    Accepted Answer

    @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.

Answers

  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949

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

  • Dell7730Dell7730 Member, PRO Posts: 388

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

    how much is too many rules? lol

  • Dell7730Dell7730 Member, PRO Posts: 388

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

    Dang It, lol

  • mhedgesmhedges Raised on VCS Member Posts: 634

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

  • Dell7730Dell7730 Member, PRO Posts: 388

    @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.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025