Page 2 of 2

Posted: Mon Jun 15, 2009 5:07 am
by DanStutzman
Right on. I'm going to try re-installing today. I think I may have a bad VM.

Posted: Tue Sep 22, 2009 10:51 am
by KennethLee
I'm also seeing this on my old machine as well as my new clean machine which is 1 week old and has InstallAware 9 installed and some developer software. The output directory is a network drive. The build will sometimes slow down where each file takes 5 seconds. For now I've opted to building locally and then copying the files to the network which takes absolutely no time. If I let the build go on the network, it would easily take 20 minutes, while locally it would only take 1 minute. When IA actually builds fast on the network drive, it takes maybe 3 minutes. The software is only ~40mb, with ~300 files, while the project is building uncompressed with all compiler optimization settings enabled.

The funny thing is that it only happens sometimes, and when it starts being slow, it continues to be slow until I reboot or something (i'm not exactly sure when it stops).

Would the bottleneck be compiler's processing tasks on the network? I'm not sure how the installs are organized but I tried some compression on the network and it's pretty fast. I used a compression library at ultra compression level and it takes roughly 8 seconds taking files from the network and putting them on the network. Could the organization of the install files be exponentially increasing the processing time on network drives? There must be some reason for the sometimes slow speeds.

Is it possible for InstallAware to investigate and optimize that? Though it's really just a small annoyance since building locally is 20 times faster.

Posted: Thu Sep 24, 2009 3:42 pm
by neillans
To be honest, we really do not advise building on network locations ... during our installation we create a series of links (or junction points if you want to use the right term!) that "point" to the source files, which we use for building the installation image -- doing this over a network drive can be tempremantal, but mostly because we are stressing the Windows implementation :)