Performance

  • Thread starter Thread starter Jay
  • Start date Start date
J

Jay

I downloaded an example of a Windows Form (.net 2.0) that mimics part of
Outlook. It was nicely done. However, I was struck by the performance. It
was not good.

What about performance of Windows Forms that are somewhat complex?

For the last few years I have done nothing but asp.net programming. The
performance has been great. I made a brief launch into windows programming
(.net 1.x) and found that the performance was not good -- e.g., the DataGrid
or whatever it was called. This discouraged me from pursuing WinForms any
further.

Jay
 
Hi Jay,

Thanks for your post.

Based on my understanding, you are caring about the security of .Net
winform.

This topic is a somewhat big one. I will try to provide as much resource
and information as I can.

Normally, .Net is truly slower than Native code due to IL JIT, GC, strong
type etc... Based on your statement, it seems that your concern focus on
.Net Winform side, because you are satisfied with Asp.net performance.

.Net winform uses the same .Net classes and CLR as Asp.net, the difference
regarding performance should be in GUI side. And based on my experience,
the GUI performance is mainly caused by the improper use of GDI+ classes or
by placing too many controls on the Form, or improper doing of control
painting.

Currently, I can not address all the .Net performance issue in one post and
there is few resource regarding .Net winform performance.(I know our .Net
winform will release a .Net winform performance dedicate article in MSDN in
March this year)

We may discuss some specific performance issue in this newsgroup.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Jeffrey,

I've recently been getting into winform programming too, and it seems when
I initially launch an application it's memory footprint jumps up to around
20 MB. But if I minimize the application it drops to a few hundred K, then
after that (when maximised) it settles at a few meg. Why is this? If the app
isn't minimized it stays around the 20 meg level (steadily increasing). I
first thought this was something I was doing wrong, but after downloading a
lot of .net apps, I see it happen to every one I've tried.

Chris
 
This is normal Windows behavior.

An application may allocate lots of memory during initialization or
when performing other work, but Windows does not immediately release
the allocated memory back to the system when it's released by the
application because the application might soon need the memory again.

However, the memory is actually available and will be automatically
released by Windows if another application needs it, or if the
original application is minimized to the taskbar.

I suggest you try this with a few non-.NET applications and see what
happens. I just saw Forte Agent drop from 16 MB to 1 MB upon
minimization, and AvantBrowser from 16 MB to 3 MB...
 
Chris said:
I've recently been getting into winform programming too, and it seems when
I initially launch an application it's memory footprint jumps up to around
20 MB. But if I minimize the application it drops to a few hundred K, then
after that (when maximised) it settles at a few meg. Why is this?
Click to expand...

I suggest to read the two articles referenced here (the articles are written
in English language):

<URL:http://dotnet.mvps.org/dotnet/code/forms/#MemoryUsage>
 
Back
Top