- Forum
- General C++ Programming
- Visual Studio compiled program runs fast
Visual Studio compiled program runs faster in x86 than x64?
yes, things like this can happen. It can go the other way too. Depends on the code.
50% faster is an unusually big difference, though. Did you compile it optmized in both? Its easy to do a debug compile by mistake...
50% faster is an unusually big difference, though. Did you compile it optmized in both? Its easy to do a debug compile by mistake...
This is possible for some specific programs. On x64, addresses (pointers) and some instructions use more memory; this can adversely affect processor cache usage. Programs that use a very large degree of indirection (many many accesses through pointers/references) are probably more prone to this slowdown when ported to x64.
I routinely have Visual Studio (2019 Community) compile console and Win32 apps as x86 and x64. Most times there is no speed difference between the two. Sometimes the x86 app can be faster, more often the x64 app will be faster when there is a difference in execution speed.
Debug vs. Release can be a major factor, as well as what optimization level is set.
The speed differential is more common with Win32 apps than console ones, but it is still a rare occurrence.
The difference in speed can be really noticeable when the CPU is under a heavy load from other apps/services running.
Another potential bottle-neck is dynamic linking vs. static linking. Dynamic DLL loading can take some time as the library is needed. VS defaults to dynamic linking so the .exe file is smaller than one that is statically linked.
It isn't just VS. MinGW/Code::Blocks can also have execution differential issues.
So, yeah, it isn't just you.
Debug vs. Release can be a major factor, as well as what optimization level is set.
The speed differential is more common with Win32 apps than console ones, but it is still a rare occurrence.
The difference in speed can be really noticeable when the CPU is under a heavy load from other apps/services running.
Another potential bottle-neck is dynamic linking vs. static linking. Dynamic DLL loading can take some time as the library is needed. VS defaults to dynamic linking so the .exe file is smaller than one that is statically linked.
It isn't just VS. MinGW/Code::Blocks can also have execution differential issues.
So, yeah, it isn't just you.
| What happened to the OP's original post? |
You can find it here.
https://www.reddit.com/r/cpp_questions/comments/lhdl4c/visual_studio_compiled_program_runs_faster_in_x86/
He/she decided to add spam links after getting your attention.
Topic archived. No new replies allowed.