CPU Killer

[Jannie du Preez]

Is there a way I can see what component is killing my CPU, It seems to be
due to a graphical component since the CPU runs at about 5% until I select a
specific TAB, I am iterating a while loop at 10 times a second, is there a
way of slowing down the graphical refresh rate.

Thanks

Jannie

[altenbach]

Well, what kind of code runs when that tab is selected?

Are you updating e.g. a graph with gigabyes of data with each iteration? What else happens in that while loop? Can you attach a simplified version of your code?

[tst]

I have seen this happen in the past when writing to the Strings[] property of a ring which is inside an array. Such a construct created problems even when a different page of the tab control was selected. To determine the culprit you can try scrolling the display and seeing when the CPU usage goes down (should happen when the control is moved off the screen). Then you can update that control only when there is a change or at a slower rate.

[Jannie du Preez]

I feel that I need to add a bit more information to enable someone to have an idea of what the problem is, (other than my not so much to be desired skills with LabVIEW that is)

The application I have built is small, consisting of 3 loops, loop one runs at once a second, loop two runs at ten times a second and loop three is adjustable according to a preset value. In loop two I have a tab control with three tabs, on one tab the application goes to 100% processor load, this tab consists of two dials, three bar graphs and two buttons, what puzzles me is the following.

1: When I select the tab that annihilates the processor, nothing has changed in the application except what is being displayed on the TAB?

2: Can a graphical component be so processor intensive? Is there a way to slow it down?

3: Is there a way I can find what component is using the processor recourses so badly.

I am stumped, any suggestions or may be there is some literature out there around dealing with excessive processor usage.

Thanks

Jannie





"Jannie du Preez" <me@home.com> wrote in message news:e4o2mi$jb3$1@newsreader02.ops.uunet.co.za...
> Is there a way I can see what component is killing my CPU, It seems to be
> due to a graphical component since the CPU runs at about 5% until I select a
> specific TAB, I am iterating a while loop at 10 times a second, is there a
> way of slowing down the graphical refresh rate.
>
> Thanks
>
> Jannie
>
>

[tst]

---

@Jannie du Preez wrote:

...this tab consists of two dials...

---

LV does the graphical processing on its own to maintain compatibility between platforms. That means that it is not the fastest when it comes to graphical displays. Particularly problematic are overlapping elements. The dials are round, but their overlapping area is the rectangle for the entire control, so you need to make sure they don't overlap.

---

Is there a way I can find what component is using the processor recourses so badly.

---

It would be helpful if you read the answers. I already answered that.

If this still doesn't help you, you should upload your code.

[Jannie du Preez]

Thank you, I give it a try

Jannie



"tst" <x@no.email> wrote in message
news:1148220608069-368260@exchange.ni.com...
> Jannie du Preez wrote:...this tab consists of two dials...
>
>
> LV does the graphical processing on its own to maintain compatibility
between platforms. That means that it is not the fastest when it comes to
graphical displays. Particularly problematic are overlapping elements. The
dials are round, but their overlapping area is the rectangle for the entire
control, so you need to make sure they don't overlap.
>
>
> Is there a way I can find what component is using the processor recourses
so badly.
>
>
> It would be helpful if you read the answers. I already answered that.
> If this still doesn't help you, you should upload your code.

[Jannie du Preez]

No that's not it. can you tell me if you open a certain tab on a VI what
changes other than the data that is displayed?

I mean all I have is seven components; there is no way that they can bring a
P4 to its knees.



"Jannie du Preez" <me@home.com> wrote in message
news:e4pt4h$ld5$1@newsreader02.ops.uunet.co.za...
> Thank you, I give it a try
>
> Jannie
>
>
>
> "tst" <x@no.email> wrote in message
> news:1148220608069-368260@exchange.ni.com...
> > Jannie du Preez wrote:...this tab consists of two dials...
> >
> >
> > LV does the graphical processing on its own to maintain compatibility
> between platforms. That means that it is not the fastest when it comes to
> graphical displays. Particularly problematic are overlapping elements. The
> dials are round, but their overlapping area is the rectangle for the
entire
> control, so you need to make sure they don't overlap.
> >
> >
> > Is there a way I can find what component is using the processor
recourses
> so badly.
> >
> >
> > It would be helpful if you read the answers. I already answered that.
> > If this still doesn't help you, you should upload your code.
>
>

[smercurio_fc]

As tst suggested, you should upload your code. We can either play guessing games all day long or we can actually look at the actual code. Also indicate with LV version you're using and which OS.

[Jannie du Preez]

Just a little bit of info. Every time a propery node is called it brings the
application thread back to graphical mode and takes the value from the
phisical control and not from memory so if you use a lot of these and try
and dislay the components at the same time, your processor usage will show
it.

[tst]

While LV can be slow, a simple display should not cause increased CPU usage, even if you're using a lot of property node. Once again, unless you post your code we can't help you.