application performance

[Drstein99]

I've been developing an application for the last 9 months on a loaded machine. today I got the chance to install and operate on it's destination pc, which is a pentium 2 300 w/ 128 meg of ram.

 

It's basically a windows application, that uses an odbc data source (mySql). There are a couple custom .dll's it uses to interface with network applications. Many buttons on the screen, and textbox controls, basically for data entry.

 

---------

 

The application runs at a snails pace which is unacceptable. the screen refreshes the buttons one at a time, and looks like i can actually see windows drawing the frames, etc...

 

The entire time the hard disk is going bezerk, and I am constantly waiting for the app to process the next button click event.

 

Most everything is in memory, until the end when i hit the commit button and sends and recieves data from mySQL server.

 

is there a switch or option i'm supposed to set in the release version, to cut down on some extra debugging activity or logging that may occur? because it's doing alot of unecessary disk activity that I can see. It doesnt run like a normal application, for example - microsoft word.

 

Please advise, thanks.

[PlausiblyDamp]

Are you doing a release build of your application? You should be able to select Debug or Release from the toolbar - then do a build.

[michael_hk]

Debug.Write calls won't affect the performance of your final release.

 

From doc.

You can write run-time messages to the Output window using the Debug class or the Trace class, which are part of the System.Diagnostics class library. Use the Debug class if you only output in the Debug version of your program. Use the Trace class if you want output in both the Debug and Release versions. For more information, see System.Diagnostics Namespace.

[Drstein99]

Where does the debug output go, where would I look that stuff up? because i'm already writing to console.writeline.

 

Debug.Write calls won't affect the performance of your final release.

 

From doc.

[PlausiblyDamp]

Debug output goes to any attached debugger - if you are running your application from the IDE then it will normally be the Output Window, although you can access this information in other ways.

When you do a release build the Debug. calls should be removed from the executable.

If you monitor your application (either through window's performance monitor or a 3rd party tool like Process monitor what kind of memory allocations / Garbage collections / CPU usage are you getting?