When moving around undocked RadPanes, I am seeing very high CPU usage - around 70% according to the Windows Task Manager. My app is a very basic one with some RadDocking controls, and very little else - almost no procedural code. My CPU is a Core2Duo E6750, and my GFX card is a GeForce GTS450. When I drag the main window around, the CPU only jumps to around 10%. I'm running a release build.
Any idea why I'm seeing such high CPU usage? Could I be doing something wrong?
For reference, doing the same thing in the Telerik Demo app causes a CPU usage of about 35% - so about half what my own app takes, but still very high for such a basic operation.
Thanks
Tom Davies
Peavey Digital Research
9 Answers, 1 is accepted
The Docking control is using a big transparent window to host its ToolWindows and compasses and this causes performance problems especially on Windows XP, on higher resolution and multiple monitors. As I said in the other ticket, we are planning to target this problem, but its cause is deep in the architecture of the Docking control (it was initially developed for Silverlight where there are no windows floating out of the application area) and this makes the problem hard to fix.
Our online examples are xbap applications where there is not such performance problem.
George
the Telerik team

Thanks
Tom Davies
As Georgi said the problem is deep in the architecture of the Docking control and it will not be easy to fix it. Nevertheless we will try to fix as soon as we can - it is already marked as a priority task.
Regards,Miroslav Nedyalkov
the Telerik team

Dragging a floating pane with no more than 3 simple controls (textbox, button, textbox, if I recall correctly) is slow, but that I can live with. However, when moving the mouse over a floating pane, the mouse cursor lags appreciably, so much that it is even difficult to click on the desired control. This makes RadDocking useless for us, and we will need to have a timeframe for the fix or start considering other docking solutions.
I am running WindowsXP on a Xeon E5430 workstation with NVidia Quadro NVS 290.
Thanks,
Jose Iborra
Quantitative Strategies - Credit Suisse

We really need a time estimate for this fix. I am under pressure to deliver an application with a workable docking system within a strict deadline. If this is not going to be resolved in time, I need to start investigating other frameworks (or think about writing my own from scratch) for docking in the very near future.
I accept that you may not be able to fix it soon, but please, can we have some time estimates so that we can look into alternatives if we need to?
Thanks
Tom Davies
Peavey Digital Research
We are planning to work on this issue for the Q1 2011 release and the performance problems will be targeted for the middle of February (the beta version).
All the best,Miroslav Nedyalkov
the Telerik team

Tom Davies

Tom Davies
Unfortunately the fix is not ready yet. You could find the full answer on this thread http://www.telerik.com/community/forums/wpf/docking/docking-fixed-in-new-release.aspx.
Regards,Miroslav Nedyalkov
the Telerik team