Различие в производительности между блоком.NET, созданным в режиме отладки и выпуска?

Question

Различие в производительности между блоком.NET, созданным в режиме отладки и выпуска?

Вот мое решение, которое предполагает проверку wp-content

# Ignore everything except directories
*
!*/

# except everything in the child theme and its required plugin
!/themes/mytheme-child/**
!/plugins/my-plugin/**

# and this file
!.gitignore

и тестирование:

git version 2.20.1 (Apple Git-117)
$ git check-ignore -v .foo foo foo/ themes/foo themes/foo/bar themes/mytheme-child \
themes/mytheme-child/foo plugins/foo plugins/my-plugin plugins/my-plugin/foo .gitignore
.gitignore:2:*  .foo
.gitignore:2:*  foo
.gitignore:2:*  foo/
.gitignore:2:*  themes/foo
.gitignore:2:*  themes/foo/bar
.gitignore:2:*  themes/mytheme-child
.gitignore:6:!/themes/mytheme-child/**  themes/mytheme-child/foo
.gitignore:2:*  plugins/foo
.gitignore:2:*  plugins/my-plugin
.gitignore:7:!/plugins/my-plugin/** plugins/my-plugin/foo
.gitignore:10:!.gitignore   .gitignore

, поэтому оно корректно игнорирует все, что я не хочу, и ничего, что я хочу сохранить.

Выпуск кода

Gitlab настроен с зеркалами репозитория для защищенных веток, в соответствии с https://docs.gitlab.com/ee/workflow/repository_mirroring.html

Когда код передается в защищенную ветвь, он будет зеркально отражен на промежуточных промежуточных и производственных серверах в голом репо /opt/checkout/repo.git/. Следующий хук post-receive (в /opt/checkout/repo.git/hooks/post-receive) затем извлечет код в рабочий каталог.

#!/bin/bash

BRANCH=staging
GIT_DIR=/opt/checkout/repo.git
GIT_WORK_TREE=/opt/bitnami/apps/wordpress/htdocs/wp-content

# on push, checkout the code to the working tree
git checkout -f "${BRANCH}"

# ensure permissions are correct
sudo chown -R bitnami:daemon "${GIT_WORK_TREE}"
sudo chmod -R go-w "${GIT_WORK_TREE}"

Для получения дополнительной информации см. https://www.digitalocean.com/community/tutorials/how-to-set-up-automatic-deployment-with-git-with-a-vps

14

.net

задан Jim 19 May 2009 в 17:12

7 ответов

If you look at the IL code generated for Debug and Release builds the differences are generally quite small. Most of the differences lie in additional nop commands at key source points to support Edit and Continue and source line debugging. However when the .NET runtime actually JITs the MSIL the runtime assembly is almost identical. The biggest difference comes when a debugger is attached. That will prevent the JIT from optimizing the actual running code.

Release versions are often much smaller as well because they just don't include as much code. There's can be patches of code surrounded with #if DEBUG statements as well as Conditional attributes that instruct the compiler to omit calls to methods in release mode (Like Debug.WriteLine).

I've found that the Debug.WriteLine and Trace.WriteLine methods, when left in production code and have a significant performance implications even if a debugger is not attached.

4