LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I have an labview application which takes around 50% of CPU usge but wen the same is running throgh code it takes only maximum of 12-16% can any body suggest me what might be the wrong.

Solved!
Go to solution

Not looking at the code but reading the reactions...

 

Could this be solved with a strategic wait in a loop somewhere?

 

When moving between development and the exe we have more threads available to hammer the CPU and the default number of threads for LV is well below 100.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 21 of 36
(1,708 Views)
There are a zillion parallel loops and they are all throttled by SQL queries.
=====================
LabVIEW 2012


0 Kudos
Message 22 of 36
(1,701 Views)

Steve Chandler wrote:
There are a zillion parallel loops and they are all throttled by SQL queries.


 

OK.

 

Wrapping the SQL queries in a sub-VI may also help but I will have to tune this week-end to find out what happened to Batman.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 23 of 36
(1,696 Views)

C'mon guys. This whole thing could be solved if NI would just implement zoom!

Message 24 of 36
(1,683 Views)

Dear all.... anyways... what the code i made is according to my application requirement.... without altering the code i got the cpu usage of my appliction lowered...  just i split my application into two... it serves my purpose..

 

 

 

Thanks for the Soupport

 

 

Rgds

Bhargav

0 Kudos
Message 25 of 36
(1,633 Views)
Solution
Accepted by Bhargavsatya

@smurthy wrote:

Dear all.... anyways... what the code i made is according to my application requirement....


I'm not even sure how to respond to a comment like this.

 

All I can think of: So your application requirement is to write convoluted code that requires a screen the size of Texas to see it?

 

I can also see that the basic response was "I'm going to ignore all of the valid and valuable criticisms and suggestions that were made and just do it my way".

 

OK. Good luck.

Message 26 of 36
(1,612 Views)

Smiley Happy

 

We are all smart alecs, but no one rewrites her/his code. Smiley Very Happy

 

Best regards,

 

Balze

0 Kudos
Message 27 of 36
(1,591 Views)

I just found out about this thread today. I want to figure out how smurthy got into this situation.

 

smurthy (if you're still reading this thread):  Did you start this application with a blank VI?  And what kind of LabVIEW training have you had up to this point?  Is this your first reasonably-sized LabVIEW application?

 

Ultimately, we want to see this kind of application solved with a cleaner architecture.  I'm looking into ways of making it easier to start off with a good framework for an application (as opposed to starting off with a blank VI).  If you're willing to provide me with these details, it will help me make future changes in LabVIEW that will help users like yourself design more modular, maintainable applications.

0 Kudos
Message 28 of 36
(1,568 Views)

Hi ..

 

 I got the solution in order to reduce the memory usage of my application.. i tried out manyways to do it.. finally i increased delay in the 100 while loops and my cpu usage is now maximum 12% for whole application... at any cost i cant reduce my code as i need to pop up 100 vi's wen alarms occured....

 

 

Rgds

Bhargav

0 Kudos
Message 29 of 36
(1,519 Views)

Hi smurthy,

 

are you sure you need 100 different VIs popping up?

Maybe you can use one reentrant VI for that purpose?! (I'm pretty much sure!)

 

Best regards,

 

Balze

0 Kudos
Message 30 of 36
(1,516 Views)