I am asking in terms of performance
我在性能方面提出要求
Which would run fastest on the server (windows server 2012 r2 - 24 cores - 64 gb ram) - serving pages fastest way - reducing load times
这将在服务器上运行最快（Windows Server 2012 r2 - 24核 - 64 GB RAM） - 以最快的方式提供页面 - 减少加载时间
Asp.net website project , c# , .net 4.5 , visual studio 2013 update 3
Asp.net网站项目，c＃，。net 4.5，visual studio 2013 update 3
I don't need site to be updated-able
我不需要网站可更新
I don't care how many or how big files to be deployed
我不关心要部署多少或多大的文件
Here the options available
这里有可用的选项
1 个解决方案
#1
14
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.
- 允许预编译的站点可更新。如果不设置此复选框，页面和用户控件（.aspx，.ascx和.master文件）将按原样复制到目标文件夹，并且可以作为文本文件进行更新，而无需重新编译项目。否则，将删除页面和用户控件的HTML标记并将其编译到程序集输出中。 http://msdn.microsoft.com/en-us/library/hh475319(v=vs.110).aspx这可能会导致非常小的性能损失，因为必须打开和处理其他文件。
- 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.
- 合并选项将文件合并到单个程序集中将导致在运行时处理最少数量的单独文件。我还没有找到有关性能影响的文档，但我怀疑单个程序集可以提高性能。
#1
14
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.
- 允许预编译的站点可更新。如果不设置此复选框，页面和用户控件（.aspx，.ascx和.master文件）将按原样复制到目标文件夹，并且可以作为文本文件进行更新，而无需重新编译项目。否则，将删除页面和用户控件的HTML标记并将其编译到程序集输出中。 http://msdn.microsoft.com/en-us/library/hh475319(v=vs.110).aspx这可能会导致非常小的性能损失，因为必须打开和处理其他文件。
- 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.
- 合并选项将文件合并到单个程序集中将导致在运行时处理最少数量的单独文件。我还没有找到有关性能影响的文档，但我怀疑单个程序集可以提高性能。