08-17-2010 12:31 PM
Is there any good reason a VI will start bogging down? My CPU usage will be running along fine at ~40% and then drop to ~10%, at this point my VI will quit responding or if it does respond it's very sluggish. I'm running WinXP and LV2009. It only seems to happen after I've been running for an hour or two, but once it happens the first time... every 5-10 min things will just quit responding normally. Anyone have any thoughts?
Thanks!
Chad
08-17-2010 12:36 PM
Watch your memory usage using the Windows Task manager.
That description is the clasic "Running in Virtual Memory" symptom since the process is placed in a Page Fail wait state while the hardware pages in the data from disk.
Ben
08-17-2010 12:52 PM
Do you have code to look at? Other wise we can just guess at what happens.
Array getting to big
Run out of memory
calling something over and over causing memory problems
etc...
08-17-2010 01:07 PM
Is there a suggested route to take to correct this problem? ...a basic solution since this is a "classic" issue. 🙂 ...or better yet, is there a write up that would allow me to learn more about this issue and how to solve it?
Ok, after doing a quick search I found that there is the Tools/Profile/Performance and Memory... tool... Looks like it might be a place to start, unless there are other suggestions?
THX
C
08-17-2010 01:12 PM
@chuggins143 wrote:
Is there a suggested route to take to correct this problem? ...a basic solution since this is a "classic" issue. 🙂 ...or better yet, is there a write up that would allow me to learn more about this issue and how to solve it?
Ok, after doing a quick search I found that there is the Tools/Profile/Performance and Memory... tool... Looks like it might be a place to start, unless there are other suggestions?
THX
C
Start there.
I suspect the exact answer to your question can be found in one of these tagged threads which I encorage anyone interested in performance to review.
If you have trouble ID the offending code, post back with what you have learned (and code by the way) so others can offer further assistance.
Ben
08-17-2010 01:15 PM
Well-
Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is memory leak issue is a start. Is the memory usage increasing during execution?
AEtest suggested showing some code- We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it." Although- we haven't really identified a "Cause" yet.
08-17-2010 01:28 PM
@Jeff Bohrer wrote:
Well-
Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is memory leak issue is a start. Is the memory usage increasing during execution?
AEtest suggested showing some code- We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it." Although- we haven't really identified a "Cause" yet.
Good! Then it is not too late to still guess.
I sense a build array in a loop.... but the image is now starting to fade.
Well that's my guess.
Ben
08-17-2010 01:32 PM
@Ben wrote:
@Jeff Bohrer wrote:
Well-
Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is memory leak issue is a start. Is the memory usage increasing during execution?
AEtest suggested showing some code- We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it." Although- we haven't really identified a "Cause" yet.
Good! Then it is not too late to still guess.
I sense a build array in a loop.... but the image is now starting to fade.
Well that's my guess.
Ben
That was the feeling I was getting from the keyboard too. The vibrations just seemed to say that.
08-17-2010 01:37 PM
@aeastet wrote:
...
That was the feeling I was getting from the keyboard too. The vibrations just seemed to say that.
If we ever meet, remind me that I owe you a beer.
Ben
08-17-2010 01:40 PM
I print this page and have it on record.