Hi,
Just saw your post about WPF Performance issues. I would like to give down few point about WPF here.
WPF uses "Painter's Algorithm" to draw the screen and this is a very simple algorithm. But this algorithm performed poorly on the hardware which was available at that time so different algorithms were invented to support the hardware and GDI uses one of those algorithm. So why Microsoft used Painter's Algorithm is because with todays graphics hardware this model performs relatively fast.
So I feel this is the reason your WPF program performance is not as expected because I don't find any flaws in your code. I would also like to know what is the graphics hardware your using If it supports Pixel Shader 2.0 then you should not get this performance problem. WPF also renders with Anti-aliasing so these are the constraints towards the performance.
Another point is if you want to measure the performance of a .Net application you an use the Stopwatch class which is available from .Net 2.0.
Simply do this
Stopwatch sw = Stopwatch.StartNew();
// Code to measure performance
sw.Stop();
Console.WriteLine(sw.Elapsed);
Suren.