x64 Debug starts quicker than Release

Question

0.00/5 (No votes)

See more:

Hi,

I have a Visual Basic .Net application I am compiling in Visual Studio 2012 (build 2 or 3) and I have found that the Release version shows the form much slower (7 seconds) than the Debug version (1 second).

Once loaded the Release version is quicker at processing. I have removed a couple of external references to see if they were causing this but they weren't.

Does anyone have any advice please?

Thanks.

Posted 22-Jun-13 0:09am

codetowns

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Answer 1 · 2013-06-22T10:53:00

If you are talking about hitting the "play" button in Visual Studio and waiting for the form to show up, then I have some idea's...

First, debug builds are incremental and do not have any compiler optimizations, which means that they will probably build a lot faster. This means that the compiler generates the code, debugger attaches, and the form pops up pretty quickly.

Release builds, depending on what you've changed, may need to be a full build, which with compiler optimizations (loop unrolling, inlining, unreferenced variable removal, etc) can take much longer to build than a debug build. This causes VS to sit there and stare at you (but there is a progress bar at the bottom), then pop up the form. Yes, this can take longer.

If you are running the program by double clicking the .EXE file in the bin\Debug or bin\Release, I bet that its not noticeable with the time difference of executing the two files. The release one may process faster though after it starts up. It really depends on your code that happens before it shows the first form, since the interpreter has to go through and JIT the code.