Which options are the most performance way of publishing asp.net website project - deployment

From my understanding:

• Delete all existing files prior to publishing will prevent old/stale files from previous publish runs from hanging around. Saves some disk space and keeps things clean. No significant performance impact (unless you start to run out of disk space).
• Precompile during publishing is probably the largest performance gain. If not checked, code backing your pages/views will be compiled when first hit, causing a delay for the first user to hit each page.
• Allow precompiled site to be updatable. Without setting this checkbox, pages and user controls (.aspx, .ascx, and .master files) are copied as-is to the target folder and can be updated as text files without recompiling the project. Otherwise, the HTML markup for pages and user controls is removed and compiled into the assembly output. http://msdn.microsoft.com/en-us/library/hh475319(v=vs.110).aspx This would likely cause a very minor performance hit, as the additional files must be opened and processed.
• Merge options Merging files into a single assembly would result in the least number of separate files to be processed at runtime. I have not found documentation on the performance impact, but I suspect a single assembly would allow for a minor performance improvement.