wcf服务的Release版本和Debug版本之间的区别，CPU占用更多空间 [英] difference between the Release build and Debug build of wcf service and CPU occupies more space

问题描述

我已经编写了一项wcf服务，该服务占用更多的CPU空间，为了减少更少的CPU空间，我需要验证哪些强制检查才能完成，请让我知道Release Build和Debug Build之间的区别.提前谢谢.

问候
Murty

Hi,

I have written one wcf service, which occupies more CPU space, what are the mandatory checks i need to verify to decrease the less CPU space and please let me know difference between the Release Build and Debug Build. Thanks in advance.

Regards
Murty

推荐答案

在调试版本中，会发出完整的符号调试信息，以在调试应用程序时提供帮助，并且也不会考虑代码优化. 在发行版中，不发出符号调试信息，并且优化了代码执行.
另外，由于在发布版本中未发出符号信息，因此最终可执行文件的大小小于调试可执行文件.

由于编译器的优化，内存布局或初始化的差异，人们可能会在发行版本中看到有趣的错误.这些通常称为Release-Only bugs.

就执行速度而言，发布的可执行文件肯定会执行得更快，但并非总是如此.

In a debug build the complete symbolic debug information is emitted to help while debugging applications and also the code optimization is not taken into account.
While in release build the symbolic debug info is not emitted and the code execution is optimized.
Also, because the symbolic info is not emitted in a release build, the size of the final executable is lesser than a debug executable.

One can expect to see funny errors in release builds due to compiler optimizations or differences in memory layout or initialization. These are usually referred to as Release - Only bugs.

In terms of execution speed, a release executable will execute faster for sure, but not always will this different be significant.

这篇关于wcf服务的Release版本和Debug版本之间的区别，CPU占用更多空间的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！