Slide bars slow EVERYTHING​, I dont understand​!!!!!

Question

I have couple of scroll bars in my VI. It's big, and it does many things, millions of things, and well does.A big program that is.
However I when I needed to add couple of scrollbars it just SLOWS EVERYTHING miserably. And my CORE 2 Duo loaded FULL just because of couple of scroll bars!
I don't understand why slide bars in Labview are that SLOW? What's wrong with it?
This is just an example of my code, in attachment.
It is placed inside the loop. And the iteration of loop is set by a 100ms timer. But when I enable peace of this code, it BARELY does two executions in a second. When I disable it does about 10 executions just as intended, although the rest part of the code is bazillion times bigger and complex.
Any clue?? Or replacements??
Attachments:
Slide bar slow omg.PNG ‏8 KB

Answer 1

Look, we are trying to help here, but you need to cooperate too.
Nobody will steal you ingenious algorithms and sell them on e-bay. Nobody will laugh at your code. However, if you are lucky, some of it might get a honorary mention in the Rube Goldberg thread. That's considered an honor!
If you feel sick, you don't fax a picture of your finger-tip to the doctor for a full differential diagnosis. Right? So why attach a code image of an area covering only 1/bazillion'th of the code. Obviously, you cannot tell what's important for us, else you would also have shown a picture of the overlapping controls of the front panels.
Many here have 10+ years of programming experience and we've seen it all. We've seen the code with a bazillion property nodes and overlapping controls. Since each property node forces a switch to the UI thread and needs to execute synchronously, your style of programming (if we can call it that) alone can be 3-5 orders of magnitude more demanding on computing resources. If you keep programming like that, you'll run into the wall 1000x earlier than with equivalent efficient code. The community here is good at identifying performance issues. Just recently we were able to take a VI that took several hours to execute and tuned it so it did the same thing (actually more) in under 10 milliseconds.
If we don't see the code, our hands are tied. I cannot debug a picture.
If your stamp sized snippet is of any indication, you are one of these newbie LabVIEW programmers that have all controls and indicators nicely parked and disconnected in an empty area of the diagram, while the loop code reads and writes everything via value property nodes. I was hoping it's not, that's why i wanted to see the code. It is likely that you are (somewhat) experienced in text based code, which often causes issues when transitioning to graphical code. You tend to stick to old paradigms that are no longer suitable in the new environment. I strongly recommend to listen to our advice and change your coding habits as soon as possible. Once you get really used to bad habits, it will be more difficult to change.
As with any advice, you have two viable options. (1) take it. (2) leave it.
So, back to the problem at hand: Were you able to solve the problem? Do you still want us to help?
LabVIEW Champion . Do more with less code and in less time .