Maximum program size

[Ray.R]

There is excellent information within this thread.

I will also be building an application which will use large-sized array. As part of a trend prediction algorithm.
Thanks for the "heads-up".

I didn't realize the limitation on LV versions 6.1 and older. Most clients have at least 7.0, but there are some with 6.1 still.

Thanks for sharing such valuable information.

Ray

[DFGray]

Ben,

Here is what little I know about the questions you asked.

1. I don't think “root” with respect to the block diagram is an official LabVIEW term. I used it in the sense of the top level of a nested structure, as mentioned in an earlier post. Internally, things like case structures and while loops have individual block diagrams per pane.


2. I do not know whether or not you will see the memory limitation on RT. It may allow you to get to the theoretical maximum of LabVIEW instead of limiting you to about 1GByte, since RT is a leaner, more efficient system than XP, but I really don't know. It is a moot point in most cases, however, since most RT systems don't have anywhere near 1GByte of RAM (although that is changing). I would strongly suspect RTX has the same limitations Windows does, since it runs on top of/ under Windows. But, once again, I really don't know.


3. Executables run in a process separate from the development environment, so you should be able to get more effective RAM that way. If I remember correctly, each EXE launches into a separate process unless you take steps to do otherwise. So, theoretically, you could launch several processes to squeeze every last drop of available RAM from your unsuspecting computer. You will have to deal with interprocess communication issues, but those are tractable. I have not tried this, but it sounds like fun...


4. I have no clue. Given the answer to #3, you may not need to.


5. I think so, but I haven't tried and LabVIEW is great at keeping you humble.


6. No clue.


7. There is probably something, but I don't know what it is. My standard method of checking is to force the VI to run in the UI thread (using Execution properties) and then look at performance vs. the normal usage.

My apologies for not answering most of your questions. Most of my experience has been with Windows until very recently.

[Ben]

Thank you for the reply Sir!

If you were not already a "Knight of NI"

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=79&jump=true

you would have earned a nomination for your contributions in this thread.

Your posting this info two days before I ran into the problem was excellent work.

I would have been on the phone screaming BUG and the poor AE's would be wondering were they could get a couple of Gig of memory to try out my example.

Thank you,

Ben