Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / December 2004

Tip: Looking for answers? Try searching our database.

Debug vs Release Memory Allocation Performance Issue

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
spiff - 30 Jun 2004 06:13 GMT
We are migrating from VC++ 6 to VC++ 2003. It is a plain, unmanaged application with both C and C++ source. When running the debug build, even outside the debugger, the memory allocation/deallocation performance appears to be orders of magnitude slower than in VC++ 6. The release build runs fine - no performance problems.

We've rewritten some of the code to do fewer memory allocations/deallocations and that has helped those pieces. However, the application is about 400K lines of code, so we'd obviously prefer not to have to reengineer the entire codebase.

Are there any compiler switches or macro definitions that will speed up the debug memory manager? Basically, what we want is the same performance that we were able to get when building with VC++ 6.
Balaji J - 30 Jun 2004 09:37 GMT
First of all what is the problem if the debug version runs slower than the release version, as the release version is the one that going to be shipped. Send the compiler options used for the debug build so that one can see what really is the compiler option that causes the program to run slowly.

Balaji.

> We are migrating from VC++ 6 to VC++ 2003. It is a plain, unmanaged application with both C and C++ source. When running the debug build, even outside the debugger, the memory allocation/deallocation performance appears to be orders of magnitude slower than in VC++ 6. The release build runs fine - no performance problems.
>
> We've rewritten some of the code to do fewer memory allocations/deallocations and that has helped those pieces. However, the application is about 400K lines of code, so we'd obviously prefer not to have to reengineer the entire codebase.
>
> Are there any compiler switches or macro definitions that will speed up the debug memory manager? Basically, what we want is the same performance that we were able to get when building with VC++ 6.
Emmanuel Claus - 02 Dec 2004 16:45 GMT
Hello,

We had the same problem ... this link should help you
http://support.microsoft.com/default.aspx?scid=kb;EN-US;833608

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.