Performance - Console vs. GUI

From: Dave M. (nospam_at_ihatesmap.com)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 15:53:43 -0700

Anyone have any updated information on application performance, specifically
GUI-based versus console-based?

I am developing an application. This application will load an XML file that
represents a script of commands that are executed against a server (basic IP
communication). The application will spawn 1 - 50 threads, and each of
these threads will get the next available step and execute it, finish, check
for another step, etc.

My question is that this application is going to main information down to
the thread level. Thread 1 executed # of commands, # passed, # failed, and
the amount of time it took. Will there be that drastic of a performance hit
by doing a GUI application versus a console application? The biggest
differences will be 1) resources to draw and maintain the GUI itself (if I
put some controls and such that require rendering) and 2) maybe allowing the
user to "refresh" statistics to see what's going on right now.

Adding .0001 to every transaction is not that big of a deal from my
perspective. But the potential is there for this thing to be running for
days or weeks. If the machine starts to bog down severely after that time
(if it would happen if a GUI environment versus a console application), that
is a problem. The operating environment is Windows 2000/XP, regular SQL
Database calls, etc.

Not sure what else is needed. Basically there are people that say GUI is
fine, others that say GUI will hinder performance. User's preference is not
considered important (isn't life grand!). Just stability and performance.

Thanks for any insight.

Relevant Pages

  • Re: How do you inherit DOS console in Win32 application?
    ... > How do you inherit and continue using the existing command-line ... > Win32 assembly console application? ... Get these handles using the "GetStdHandle" API, ... But the main gripe here is technical...as you've noticed, a GUI ...
    (alt.lang.asm)
  • Re: Model View Controller basics.
    ... >don't have the skills to do so. ... write your phonebook application without any GUI. ... Instead give it a console interface. ... Then write a completely separate module (a controller) that *knows* ...
    (comp.object)
  • RE: Interop: C++ Console & C# GUI
    ... the GUI of application that interact with the console. ... The GUI must access some methods included in libraries and exposed by ... It's not clear if the GUI is talking to your console app in any way. ... GUI code makes some decision on updating controls. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Interop: C++ Console & C# GUI
    ... A web service would be a really heavy way to do this, ... the GUI of application that interact with the console. ... The GUI must access some methods included in libraries and exposed by ... I have thinked to to link GUI with WebService "A" that communicate ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Screw Linux, Im going back to Windows!
    ... so I presume GUI is my best option. ... >> or does using the console teach you how things work at a lower level, ... > There are lots of reasons why people use shell ... > One main reason is to execute shell scripts. ...
    (comp.os.linux.security)