jQWidgets Forums

jQuery UI Widgets › Forums › Grid › 120 columns grid performance issue.

Tagged: ,

This topic contains 3 replies, has 3 voices, and was last updated by  Peter Stoev 10 years, 4 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    120 columns grid performance issue. Posts
  • December 26, 2014 at 5:48 am 120 columns grid performance issue. #64707

    jcode99
    Participant

    120 columns grid scrolling is too slow on IE8.
    I’m testing follow this sample with IE8 ~ IE11.
    IE8 is too slow and IE11 is little faster than IE8.
    I’m must use 120 columns on grid.
    How can performance better faster?
    Thank you.

    ———-sample code is here———–
    var datafields = [
    <% for(int i = 1; i < 120; i++){%>
    {name:”index_<%=i%>”, type:”string”},
    <%}%>
    {name:”index_120″, type:”string”}
    ]

    var columns = [
    <% for(int i = 1; i < 120; i++){%>
    {text:”index_<%=i%>”, datafield:”index_<%=i%>”},
    <%}%>
    {text:”index_120″, datafield:”index_120″}
    ]

    var source = {datafields:datafields}

    var dataAdapter = new jQuery.jqx.dataAdapter(source);

    jQuery(“#dataGrid”).jqxGrid(
    width:900,
    height:400,
    source:dataAdapter
    }

    December 26, 2014 at 3:33 pm 120 columns grid performance issue. #64713

    Peter Stoev
    Keymaster

    Hi jcode99,

    Yes, it won’t be good in IE8 with 120 columns.

    Best Regards,
    Peter Stoev

    jQWidgets Team
    http://www.jqwidgets.com/

    December 29, 2014 at 1:22 am 120 columns grid performance issue. #64746

    oneq
    Participant

    Dear Mr. Peter,

    For 4 months, we have used your product for our renewal project to extend “Open Market Seller Office web application” to Cross Browser and Mobile.
    However, now we are in trouble with applying jqwidget grid in your product. If we apply it, we meet a big problem with the speed of grid.

    You jqwidget grid has a critical problem with rendering performance.
    There are more than 30 grid column. If we apply the renderings to all those columns, we can see the performances in all web and mobile browsers become very slower.

    If we just check the performance only with your product, that problem seems to occur only when we use IE.
    IE(8,9,10,11), Chrome, Safari, Firefox
    Android, IOS

    The target of our project is to extend the function to Cross Browser and Multi Devices.
    We got a feedback from our customer who asked us to fulfill this project. After their quality test division tested our result of the project, they decided that the availability of our result of project for various devices is good but the quality of performance is low.

    If we compare our product with other products, our product’s performance is slower than Ext-JS, JQ-Grid, FlexGrid(IE-Only). In my opinion, this is because of the difference of Rendering Style.

    For example,
    1. When move from mobile to web scroll, the movement is not so smooth.
    2. Loading for the first time, if we use ‘cellrenderer’ in column, the change of scene is not smooth.

    Opinion)
    1. The part of Column Rendering in Grid is too heavy.
    2. Each every time Mouse or Data is changed, there would be various event calls.

    Even though, except those, still there are many other opinions for your product,
    Now I get too much stress because of the speed of performance.

    Isn’t there any proper way to optimize your product?

    PS :
    Your API Document just guide us with small range without regard to the real cases of work.
    To find a real cases to apply for this project is not so easy.

    It would be much better for you to raise the price and give better service.
    I am quite sure that jqwidget can succeed if jqwidget more service minded globally.

    Thanks and Regards,
    HanGyu Kim in Seoul, Korea

    December 29, 2014 at 9:58 am 120 columns grid performance issue. #64758

    Peter Stoev
    Keymaster

    Hi oneq,

    If you do not find that our product meets your project requirements, then you may step into evaluating a different product. That’s why we give 30 days free evaluation. jqxGrid is quite big Grid with hundreds of options and its performance basically depends which options are turned on and which are not. The performance is may be not the best, but is good as you can see from our online demos, some of them include 10000+ rows. If you apply as you say custom rendering functions then what do you expect? Each rendering function affects your performance. It overrides the built-in rendering logic which is optimized. Using Filter Menu is faster than using Filter Row because Fitler Row requires additional widget to be always displayed and the Filter Menu shares one Menu for all columns. Things like that affect your performance and you should make the tradeoff on your side.

    Best Regards,
    Peter Stoev

    jQWidgets Team
    http://www.jqwidgets.com/

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.