04-27-2010 09:29 AM
I'm quite new to LV, and am used to a little C programming, these kind of optimizations seem to make LV a lot less fun to use...
My PC has a 64 bit processor but only a 32 bit windows Vista, god knows why we decided to get those operating systems on them 😞
Would my problems be solved by *only* changing to 64 bit Vista's or do I still need a lot more memory (because of fragmentations?) if I stick to the same programming style?
04-27-2010 09:37 AM
Switching to x64 OS is only part of the solution. Since labview would still be 32-bit, you would only get a little extra memory (up to 4GB total instead of 2 or 3GB on a 32-bit system). You would also need LabVIEW 64-bit to benefit from the very large address space (8TB). Of course actually having enough RAM for LabVIEW and all other applications running will help speed things up a bit.
I'm thinking that there is still some optimizing to be done before thinking of this solution. Preallocating memory and knowing when memory is copied is probably the best thing to work on.
Cheers.
04-27-2010 09:38 AM
Gerritvdv wrote:I'm quite new to LV, and am used to a little C programming, these kind of optimizations seem to make LV a lot less fun to use...
My PC has a 64 bit processor but only a 32 bit windows Vista, god knows why we decided to get those operating systems on them 😞
Would my problems be solved by *only* changing to 64 bit Vista's or do I still need a lot more memory (because of fragmentations?) if I stick to the same programming style?
Without playing with your code and data sets it is hard to say with certainty.
The issue is LV wants a contiguous block for buffers so convert your code to use smaller blocks. i recently had good results with using multiple single element queues to hold pats of teh images as we processed.
Ben