Negative performance issues

3 posts, 0 answers
  1. Michael Josiah
    Michael Josiah avatar
    92 posts
    Member since:
    Nov 2007

    Posted 04 Dec 2007 Link to this post

    There seems to be a horrible performance issue with the window and dock controls. These controls just simply cant be dragged around a form gracefully. The normal Telerik ASP.NET versions work perfectly fine but the Prometheus version do not. For instance create a splitter with two panes. On the right pane and a normal prometheus window. Now drag it around. You will notice the immediate performance issue here as its a pain to drag around.

    This performance issue also effects the docking controls. Throw a splitter control in the mix and then add a docking zone and dock. Then try to move the dock window around. You will notice a very horrible performance issue with it. As with the previous error, the old controls work fine and perform very well. Even the demo version on the public website moves more sluggishly then its older ASP.NET counterpart.

    I am trying to build a prometheus only web application but with these issues I am finding it very hard to do so.
  2. Michael Tissington
    Michael Tissington avatar
    63 posts
    Member since:
    Nov 2007

    Posted 06 Dec 2007 Link to this post

    I second this - both Windows and Dock are VERY slugish in this release.
    I hope it's because it's still beta.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Georgi Tunev
    Admin
    Georgi Tunev avatar
    7207 posts

    Posted 10 Dec 2007 Link to this post

    Hi Michael,

    Generally speaking we are using the MS AJAX drag and drop implementation to move the RadWindow Prometheus / RadDock Prometheus controls. We are considering to use a movable DIV like in the Classic RadWindow for ASP.NET, but we need some more time for investigating a possible implementation.

    For the time being can you please make sure that you have set the compilation debug property to false in the web.config file:

    <!--  
      Set compilation debug="true" to insert debugging  
      symbols into the compiled page. Because this  
      affects performance, set this value to true only  
      during development.  
    --> 
    <compilation debug="false"

    Our tests show that if the debugging is switched off, this leads to major improvement in the moving behavior of the controls.

    For convenience I've attached to this thread the test setup on our side - in the sample we are using the NorthWind database for RadGrid's datasource. There are 10 grids using this datasource, 2 of them in RadSplitter's panes. In addition there are RadDock and RadWindow on the page. 



    Kind regards,
    Georgi Tunev
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Back to Top