System.Drawing - SafeNativeMethods . GdipFillRectangleI causes a lot of page faults - DOTNET

Page faults are not neccesarily bad things.

GDI+ however is fraught with performance problems. There is no accelleration
so everything is done by the CPU. For lage images this can be a major
problem.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.





<tbatwork828@hotmail.com> wrote in message
news:1131747092.569014.111090@o13g2000cwo.googlegroups.com...
> We just profiled our application and noticed that
> SafeNativeMethods.GdipFillRectangleI method (called by
> Graphics.FillRectangle) in System.Drawing causes 88% of all of our
> -soft- page faults. We are soft faulting on an order of 2000 spfs/sec
> with 10 charts - with one charts we are to 600 SPFs/sec. Both numbers
> are high. We are a charting intensive, real-time trading .NET
> application that plots real time trading data on a high frequency
> basis. Does anyone know of any performance issues with GDI drawing
> functions in .NET framework...?
>

Page faults are not neccesarily bad things.

GDI+ however is fraught with performance problems. There is no accelleration
so everything is done by the CPU. For lage images this can be a major
problem.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.





<tbatwork828@hotmail.com> wrote in message
news:1131747092.569014.111090@o13g2000cwo.googlegroups.com...
> We just profiled our application and noticed that
> SafeNativeMethods.GdipFillRectangleI method (called by
> Graphics.FillRectangle) in System.Drawing causes 88% of all of our
> -soft- page faults. We are soft faulting on an order of 2000 spfs/sec
> with 10 charts - with one charts we are to 600 SPFs/sec. Both numbers
> are high. We are a charting intensive, real-time trading .NET
> application that plots real time trading data on a high frequency
> basis. Does anyone know of any performance issues with GDI drawing
> functions in .NET framework...?
>

what are our options - do you have any code tips or do you know of any
workaround so that we can accelerate...? Can u provide any
documentation so that we can try to opimtize our code..? thx

what are our options - do you have any code tips or do you know of any
workaround so that we can accelerate...? Can u provide any
documentation so that we can try to opimtize our code..? thx

On my opinion you could have a lots of beneficts usind DirectDraw instead of
GDI+.
On some test I've done, using directdraw even with the managed directx is
quiet faster than GDI+

Regards
Cristian Mori

"tbatwork828@hotmail.com" wrote:

> what are our options - do you have any code tips or do you know of any
> workaround so that we can accelerate...? Can u provide any
> documentation so that we can try to opimtize our code..? thx
>
>

On my opinion you could have a lots of beneficts usind DirectDraw instead of
GDI+.
On some test I've done, using directdraw even with the managed directx is
quiet faster than GDI+

Regards
Cristian Mori

"tbatwork828@hotmail.com" wrote:

> what are our options - do you have any code tips or do you know of any
> workaround so that we can accelerate...? Can u provide any
> documentation so that we can try to opimtize our code..? thx
>
>