01-18-2021 12:37 AM - edited 01-18-2021 12:39 AM
Dear Community.
Thank you to everyone who reads my post.
Have you ever built a 1-second while loop with no action and run an exe file to check the memory?
it decreases slightly after another hour or so.
What I'm curious about is basically why the exe file eats a lot of memory, and if there is a way to alleviate it?
I use LabVIEW 2019 (32bit) and Windows 10 Pro 64bit.
01-18-2021 12:19 AM - edited 01-18-2021 12:34 AM
Have you ever built a 1-second while loop with no action and run an exe file to check the memory?
it decreases slightly after another hour or so.
What I'm curious about is basically why the exe file eats a lot of memory, and if there is a way to alleviate it?
I use LabVIEW 2019 (32bit) and Windows 10 Pro 64bit.
01-18-2021 01:33 AM
The LabVIEW runtime itself needs a few tens of MB to do its job. Nowadays, it does not seem very much.
What do you mean with "a lot" and why would you need to reduce it?
01-18-2021 02:00 AM
Thank you for your help!
Our software controls multiple machines.
We want to connect PC and machines with each exe file, and we implemented it accordingly.
Each connection wants to be isolated when an error occurs, and one PC wants to control as many machines as possible.
01-18-2021 02:21 AM
AFAIK there is no way to reduce the runtime footprint. I think you can still run many applications, though.
Are you using Windows or Linux? Maybe you can act on the OS side (use an industrial version, disable unused services, etc.).
01-18-2021 03:07 AM
@Jively wrote:What I'm curious about is basically why the exe file eats a lot of memory, and if there is a way to alleviate it?
You need to be much more specific. What is "a lot" and what would you consider "normal" instead?
Why don't you investigate memory use of your real applications? A empty while loop is certainly not representative. (With the same logic you could say that driving an empty 18-wheeler across the country should not use any diesel fuel at all.)
(Nothing "eats" memory. Memory usage is not a destructive process, because once the application closes, you get it all back.)
Do you have memory problems? The memory use of a LabVIEW applications is not worse than most other modern programs.
01-18-2021 03:09 AM
The meaning may have been misrepresented.
Even if you create and run "blank.exe", it uses about 45MB of memory.
Is there any way to reduce memory usage?
01-18-2021 03:15 AM
@Jively ha scritto:
The meaning may have been misrepresented.
Even if you create and run "blank.exe", it uses about 45MB of memory.
Is there any way to reduce memory usage?
Well, for ten applications this amounts to half a GB. What's the point in a, say, 16 GB machine?
01-18-2021 03:16 AM
@Jively wrote:
The meaning may have been misrepresented.
Even if you create and run "blank.exe", it uses about 45MB of memory.
Is there any way to reduce memory usage?
No. That's probably the RTE footprint.
But you could consider running the different Main VIs of the each executable in the same executable.
So instead of creating multiple executables, you 'd make one executable that runs the VIs. That would give you 45 MB + n*X?? instead of n * (45 + ???). You might have to solve some issues, as all VIs will be shared.
01-18-2021 03:54 AM - edited 01-18-2021 03:55 AM
Thank you for your interest and help.
My English is bad, so I express it with an image.
We control with exe, and asynchronous calls are not currently considered, so memory needs to be reduced.