Quantcast
Channel: VBForums - Visual Basic 6 and Earlier
Viewing all articles
Browse latest Browse all 21089

Large EXE means app runs slower?

$
0
0
I recently read a comment somewhere that stated the larger the executable, the slower the app would run. I'm wondering if there is any truth to that -- or if 'larger' was taken out of context, and the person meant 'more code' and not just the size of the EXE on disk.

I ask because I have a portable app, that must be a single EXE due to the way it is deployed, however I have a number of resources in the resource file for several dependencies (some OCX, a DLL, and a few helper EXEs as well as some additional data and ZIP files.) In sub main I extract these resources to the current directory if they don't already exist there, then continue program execution.

The speed at which the EXE starts up (due to extracting the resources) I'm sure adds a little to startup - but should only do so when my file existence checks return false. Even if I were not extracting them from the resource file, does just having them there in the resource file slow down the app's startup and/or execution?

I'm concerned because the EXE is about 9MB. Probably a good 40% of that are these embedded resources. Is this a problem? (worst case scenario I can repackage this app in a self extracting archive if it will help, otherwise I don't want to bother with the additional hassle when deploying a new version...)

Any thoughts are appreciated, and I apologize in advance for such an elementary question - I'm entirely self-taught, and my google-fu is failing me mostly finding issues about VB6 just running slower on modern Windows versions.

Viewing all articles
Browse latest Browse all 21089

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>