David_J_G
asked on
Slower App speed with Visual Studio 2013 compilation when compared to VS2008 compilation?
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.............
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.............
ASKER
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! :-(
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! :-(
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks; there was, amongst other things a 20mS (2008) wait which was set to 200mS (2013).
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.