Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Cube Grid display latency

    Hi,

    When showing a cubegrid, display time seems to increase significantly and exponentialy based on the number of distinct facet values and not on the total number of records.

    We seem to encounter issues whenever the number of values of a single facet goes over a few thousands and this leads the grid to take a few minutes to display...

    For instance, a 3000x3 grid takes much longer to display than a 300x30 grid.

    We're using a valid RestDataSource that provides records which works and does not seem to induce any bottleneck here. And once the grid is displayed, lazy loading works quite well.

    I did not provide a complete example as this would require having a complete valid DataSource, and I think it is a global issue of the component ? I still attached a sample client grid usage example.

    Can you tell us if this is related to the component itself and if there's a way to improve display time ?

    SmartGWT 3.1p Power Edition / GWT 2.5
    SmartClient Version: v8.3p_2013-03-13/PowerEdition Deployment (built 2013-03-13)
    Chrome (latest), Chromium (latest), Firefox (latest)
    Attached Files

    #2
    Multiple minutes suggests that you were probably testing performance in GWT Development mode, or with some kind of debug tools active (Firebug, Chrome developer tools). It's quite a bit faster without such tools active (as end users will see it).

    Even so, a 3000x3 grid clearly offers very poor usability and is not a case we would try to optimize for. Generally speaking, grid shapes that have good usability are the ones that display quickest.

    Our experience is that end users quickly realize that there's no point in creating a grid that stretches 300 browser widths and so do not run into a scenario that performs slowly more than once.

    Comment

    Working...
    X