11-08-2015 02:59 PM - edited 11-08-2015 03:02 PM
Long ago, I made this table to monitor the size of the runtime engine. Maybe it is time to update it. (there is also this table for LabVIEW)
LV5.1 ... 2.6MB
LV6.0 .. 10.1MB
LV6.1 .. 14.1MB
LV7.0 .. 20.2MB
LV7.1 .. 32.9MB
Lets add the newer versions (32bit standard) I randomly picked one of x.x.1, sp1, etc. for each major version):
LabVIEW 8.0 85MB
LabVIEW 8.2 89MB
LabVIEW 8.5 98MB
LabVIEW 8.6 141MB
LabVIEW 2009 172MB
LabVIEW 2010 178MB
LabVIEW 2011 213MB
LabVIEW 2012 226MB
LabVIEW 2013 257MB
LabVIEW 2014 268MB
LabVIEW 2015 274MB
Well, considering witha it does, even 274MB seems almost insignificant these days. 😄
For comparison, let's look at the size is of a modern wireless driver? Wow!!!!
238MB download (that is 4% of the entire Windows 10 download!) and almost a gig (880MB!!) needed. What else does it do besides shuffling bits into a wifi chip and back?? Is really every single bit of that download essential?
11-08-2015 07:45 PM
Keep in mind that those are download sizes. I would be interesting to see what the unpacked size turns into.
11-09-2015 01:28 PM
@crossrulz wrote:
Keep in mind that those are download sizes. I would be interesting to see what the unpacked size turns into.
Yes, but the run time engines also include additional components that are optional (Variable engine, USI, Dataocket, deployable license). Not sure what the size of the pure run time engine is.
The WIFI driver requires 880MB.
11-09-2015 02:02 PM
@altenbach wrote:
Not sure what the size of the pure run time engine is.
Jack has posted the How to Segment the Run Time Engine which shows how to break it up into the subpieces and only include what you need. The result was a runtime engine around 30MB. I think his site might be down at the moment but here is the idea exchange item, in the comments Jack links to his site where the article was.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord