If you are using SSD, even though the additional speedup from using a RAM drive may only provide a slight boost, the RAM drive also has the advantage of slightly reducing the wear and tear on your SSD (since SSD's have a limited, but large, number of write cycles). If the RAM is available,and you don't anticipate needing the RAM for other tasks while integration is processing, I think it makes sense to use the RAM drive. It might be helpful if there were some recommendations on which locations (disk properties - write and read speeds (for large and small files) and capacity) are preferred for various groups of files. For example, if you have only one traditional HDD, your integration times will probably be long, since the disk will be thrashing. Putting some of the files (perhaps updates) on a USB 3.0 flash drive might speed up the overall integration, even if the USB drive is slower. If two HDD spindles are available, which files should be located on different HDD's to minimize thrashing? If a 2GB RAM drive is available, which part of integration would most benefit from having its files on the RAM drive? I agree. Staying with DISM also has the advantage that resulting image is (as far as I know) "supportable", since it was built with MicroSoft provided tools (as long as only a subset of the WinTookit features are used).