On 25-Jan-13 10:44, Hoover, Jacob wrote: > I currently have a single MSI with ~30k components. During installations > and major upgrades it appears the sheer number of components is causing > performance issues (the files are data files so there aren't version info > headers). What is the best way of increasing installation and updates > performance without sacrificing best practices (one file per component)? > Would breaking the install into multiple MSI's provide any benefit even > though all of the MSI's would need to be installed? Would embedding the data > into multiple DLLs with version info be worth the effort? (Most of the files > are < 1kb, but I believe Windows installer hashes the files if they don't > have version info and the create and modify timestamps are the same.) Are > there any other options available? Above 7000 or 8000 components, MSI starts to exhibit really awful performance during costing. Multiple MSIs would prevent that. But it's still a problem outside of setup. One of my past projects had this problem and we decided to fix it using zip files to combine multiple data files; that fixed setup and development and testing.
-- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users