Slower App speed with Visual Studio 2013 compilation when compared to VS2008 compilation?

David_J_G
David_J_G used Ask the Experts™
on
We have a C++ application which was originally developed on the VS 2008 platform.

We have since migrated to VS2013 and are finding that when the exact same code is compiled on the VS 2013 the application runs at a substantially slower speed.

Our developers are a little stumped by this, so can anyone suggest possible reasons for this?

They have done some investigation work but have not been able to resolve the issue; we did think that VS2013 compiled projects would actually run faster than when compiled using VS2008!

I know this is a little vague so I will attempt to add data related to any further information that you might need to help us out.

Thanks in advance.............
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Karrtik IyerSoftware Architect

Commented:
Are you sure you are running the same version of build in VS 2008 at VS 2013, I mean debug  or release in both versions of visual studio? If you are running release version built in 2008 vs debug version built in 2013, that may not match. Similarly the bitness, either 32 or 64 bit built in both versions.
Also if this is not an issue, it would be good to further analyze and find out which part of the code is causing this issue using time logs and post that piece of code for us to further comment.

Author

Commented:
Thanks for the quick reply.

Yes those are basic configurations that we have already tried and double checked.

And yes we do use log time measurements to find which functions are taking longer…its…almost everything! :-(
Karrtik IyerSoftware Architect
Commented:
So if everything is slow, here is what I would do, I would write a sample console app, If we say write a simple console app to say read sufficiently large file or write to file, and build it in VS 2008 and VS 2013, to see if that is giving any different in terms of performance. There must be some library or some particular set of class when used might be resulting in slower performance.
Top Expert 2016
Commented:
debug versions may not be compared, since the debugger has changed and the newer one has much more functionality but could slow down if you didn't move to better hardware. be aware that the newer compiler may use more threads where the performance highly depends on the number of cores and especially on the amount of physical memory available.

in release mode you need to have same optimizations. check all changes you did for migration. are you using new 3rd-party libraries? or changed from multi-byte to unicode? the latter would double all space needed for strings.

try to use an ssd for both applications. first only the data(base) should be stored on ssd and perhaps the program + dll's as well. if that helped, check file or database access whether there had been changes and find out why the disk access is so much slower for the new application and its environment.

Sara

Author

Commented:
Thanks; there was, amongst other things a 20mS (2008) wait which was set to 200mS (2013).

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial