Chart rendering performance dropped (2015 Q3 vs 2014 Q3)

4 posts, 1 answers
  1. Dirk
    Dirk avatar
    25 posts
    Member since:
    Aug 2013

    Posted 12 Oct 2015 Link to this post

    Hi,

    I just upgraded my solution from Kendo UI 2014 Q3 version to 2015 Q3 and experienced a massive drop in chart rendering performance.

    Comparing both versions on the same machine (server, browser) an area chart with about 20000 data points now takes 2-3 times (Chrome: 15s vs 7s; 25s vs 10s in Firefox) more time to finish rendering.

    Why?

    Did I miss something?

    Is there a simple solution to achieve same rendering performance of the chart as in 2014 Q3 version?

     

    Regards,

    Dirk

     

  2. T. Tsonev
    Admin
    T. Tsonev avatar
    2770 posts

    Posted 14 Oct 2015 Link to this post

    Hello,

    The best way to confirm this regression would be a test case set up to closely replicate your scenario.

    A snippet in the Dojo with the configuration you're using and stub data would be ideal.
    Profiling the real application is also an option, but might be inappropriate or less convenient for you.

    Regards,
    T. Tsonev
    Telerik
     
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
     
  3. Kendo UI is VS 2017 Ready
  4. Dirk
    Dirk avatar
    25 posts
    Member since:
    Aug 2013

    Posted 26 Nov 2015 Link to this post

    Hi,
    I tried to setup a snippet as you suggested and found that the regression is caused by the rendering of the category axis labels.

    What I've found is that the chart renders at least ten times faster (which is really good!) if there are no labels at all.

    So I adopted my javascript function (al lot of calculating if and where to put labels) and set the step property for the labels accordingly from 1 to appropriate value (6, 12, 48, 720) based on chart width, amount of data, …

    My suggestion is to state in documentation that if the chart renders slowly use label settings (step property) to speed things up.

    Regards
    Dirk

  5. Answer
    T. Tsonev
    Admin
    T. Tsonev avatar
    2770 posts

    Posted 30 Nov 2015 Link to this post

    Hi,

    That's a good point. I'll add it to the documentation as it's a common explanation for poor performance.

    Even better, we could add a run-time check and log a warning into the console if it's above a certain number.

    Regards,
    T. Tsonev
    Telerik
     
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
     
Back to Top
Kendo UI is VS 2017 Ready