Flexgrid performance, strange behavior

Posted by: diegomesata on 26 March 2018, 6:33 pm EST

    • Post Options:
    • Link

    Posted 26 March 2018, 6:33 pm EST

    Hello, I want the improve the flexgrid performance, I have very fast digitizers, so they are complaining all the time about the flexgrid speed.

    I made some test, and I found that every time you change a cell, all the cells in the current view are updated and every cell value is get twice from the data model.

    1. Are there a way in that only the current row values are repainted?

    I thought that at the event cellEditEnding, setting e.refresh to false, would do the job, but NO!

    1. Why the cell values are get twice from the model?

    http://jsfiddle.net/bwdea8y3/130/

  • Posted 27 March 2018, 6:14 am EST

    Hi,

    The flexgrid is highly optimized to deliver maximum performance.

    After edits grid needs to refresh all its content which are currently rendered on the view as part of the design (since there could be hidden changes, ex:- someone may handle rowEditEnding event and also update other rows in the event)but this is optimized not to degrade the performance.

    If you are facing performance issue there might be other factors involved . Please feel free to provide more information on your use case so that we can help you accordingly.

    You can visit the following URL to check the grid’s performance:- http://demos.wijmo.com/5/angular/benchmark/benchmark/#/flexgrid

  • Posted 27 March 2018, 11:10 am EST

    Hello, do you check the fiddle? http://jsfiddle.net/bwdea8y3/130/

    Why does after editing one cell, the other cell values are get from the model twice?

  • Posted 28 March 2018, 6:34 am EST

    Hi,

    Yes, we had a look at the fiddle you provided.

    In the fiddle you provided, the performance issue can be attributed due to large no of DOM operations in getter. Once you get rid of those, grid performs much better.

    Why does after editing one cell, the other cell values are get from the model twice

    This is by design, first time it performs validation if the value exists and then returns the value if it exists.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels