Use disable structure in a Call Library function node increases execution time

[Xinghe.W]

I found that if I use a disable stureture to disable one of the output from a Call Library function node, the execution time will be dramatically increased. Is there anyone can explain this?

[billko]

I can't even think of a reason why you wnt to do that.

[X. · Accepted solution]

You may want to read this thread and the benchmarking I did there.

Turn off debugging and check whether the performance penalty you are mentioning (but not quantifying) is still there.

[Xinghe.W]

When I do debugging I like to disable parts of my code and see how the others parts work. It seems that I have to be carefull when I disable parts in a while loop.

[billko]

---

@Xinghe.W wrote:

When I do debugging I like to disable parts of my code and see how the others parts work. It seems that I have to be carefull when I disable parts in a while loop.

---

My style of debugging makes use of disabling code only to the extent od disabling suspect code and enabling alternative code; I've never used it beyond that.  But maybe that means I'm missing more subtle/more advanced methods of troubleshooting.  Could you enlighten me on why you would disable an indicator to troubleshoot, or was that just the simplest way to illustrate your point?

Thanks!  🙂

[Xinghe.W]

The code I was working on is much more bulky and there is not enough space so I decided to use a simply one to illustrate my point. Of course there is no point to disable a indicator in a while loop 🙂  

[billko]

---

@Xinghe.W wrote:

The code I was working on is much more bulky and there is not enough space so I decided to use a simply one to illustrate my point. Of course there is no point to disable a indicator in a while loop 🙂  

---

I'm always open to new ideas and didn't want to risk losing a learning opportunity.  Thanks.  🙂