We have the following scenario: - base installation with 14k files, 800MB msi file and about 1,4GB after installation - patch changing about 2k files and adding 13k files, 400MB msp file - base installation took about 5-7 minutes to install - patch took more than 40 minutes to apply (msiexec running at an average CPU load of 80%)
Only about 10MB per minute isn't normal, is it? (Using a major upgrade rather than a patch might be faster here, but the main goal right now is evaluating WiX's (and Windows installer's) patch performance.) 1. Is Windows Installer running a lot of tests while executing a patch rather than just applying the necessary changes? 2. Is Windows Installer known to perform badly when the installation has more than 20k files? 3. Are RemoveFile operations slowing down patch execution? 4. Is WiX patch generation slowed stronger by number of files or size of files to compare? 5. Does Windows Installer generally have a lousy performance when it comes to patching? 6. Are there things known to slow down patching ? (apart from very many or very large files :P) Any shared experience would be much appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/400MB-Patch-taking-more-than-40-minutes-to-execute-Is-that-normal-tp7587782.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
