MSBUILD.exe is executing very slow
Experiencing, MSBUILD.exe is taking very long time.
This command is taking 50+ min to execute: C:\Program Files (x86)\MSBuild\14.0\Bin\amd64>MSBUILD C:\xyz.sln /p:Configuration=Release /p:OutDir=c:/test
This command is taking 1 min to execute: C:\Program Files (x86)\MSBuild\14.0\Bin\amd64>MSBUILD C:\xyz.sln /p:Config=Release /p:OutDir=c:/test
Question:
1: Is that ok to use /p:Config=Release instead of /p:Configuration=Release?
2: What can be the root cause to making the build so long with /p:Configuration=Release?
1: Is that ok to use /p:Config=Release instead of /p:Configuration=Release?
I am afraid is not. Just as Lex comment, /p:Config=Release is not a valid argument. I have create a test sample with that argument, but I found that solution is build with default configuration Debug:
So the argument /p:Config=Release is a invalid.
What can be the root cause to making the build so long with /p:Configuration=Release?
As test above, when you build with /p:Config=Release, VS/MSBuild will build solution with default configuration Debug. As we know, Debug mode does a lot less optimizations, as those can mess up the mapping between instructions and lines of code. So, the compiler is doing less work there.
Even if a full debug build is slower, Debug builds happen a lot more often and can usually take advantage of incremental builds a lot more than Release build can. So fairly often a Debug build doesn't have to do nearly as much work as a Release build would. So the command with Debug configuration will take less build time.
Besides, when you first completed the build solution, you should clean the solution, otherwise, most of projects in the solution will skip building. Because most of them are up-to-date. So you should clean the solution after you build the solution first time.
In addition, if you want to know the detail info about build process, you can set the "Logging Verbosity" to the value Diagnostic by addding /v:diag to your build command line:
MSBUILD C:\xyz.sln /p:Configuration=Release /p:OutDir=c:/test /v:diag
- How to Implement an object pool in Java that does not create garbage as it grows?
- Performance degrade on JSObject after 2^23 items
- Most elegant way to find node's predecessors with networkX
- Why is bytes(lst) slower than bytearray(lst)?
- Initiate all potential props of the object right away or as you go?
- Maximizing Efficiency of Collatz Conjecture Program Python
- Making the Android emulator run faster
- Powershell version of cut -d is very slow on large files, am I missing the fast way to do it?
- Java foreach efficiency
- Why the use of name arguments in a function actually generate more code?
- Which bitset implementation should I use for maximum performance?
- Is there any performance benefit in using const or readonly modifiers on fields in c#?
- Producer consumer queue best practices and performance
- Does Java have any equivalent to C++ string_view?
- Efficient calculation of Fibonacci series
- Does the more time a function takes means its runtime complexity is larger?
- Improve INSERT-per-second performance of SQLite
- CASE vs Multiple UPDATE queries for large data sets - Performance
- how to tune out of memory exception spark
- Why does JIT order affect performance?
- Can some explain the performance behavior of the following memory allocating C program?
- How to debug a database query for performance
- Comparing two byte arrays in .NET
- Algorithm to find all the exact divisors of a given integer
- improve layout performance
- Why is processing a sorted array faster than processing an unsorted array?
- It is more efficient to use if-return-return or if-else-return?
- Bit Aligning for Space and Performance Boosts
- Terrific performance difference between almost equal methods
- Why does this simple and small Java code runs 30x faster in all Graal JVMs but not on any Oracle JVMs?