flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34467) Spark DataGrid performance extremely decreased since "gridView" is introduced.
Date Fri, 12 Dec 2014 05:15:13 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243724#comment-14243724

Alex Harui commented on FLEX-34467:

FLEX-34644 found that the DG was creating a display object that was sized relative to the
number of items in the data provider.  Please re-test and see if the fix for FLEX-34644 also
fixes this issue.

> Spark DataGrid performance extremely decreased since "gridView" is introduced.
> ------------------------------------------------------------------------------
>                 Key: FLEX-34467
>                 URL: https://issues.apache.org/jira/browse/FLEX-34467
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>    Affects Versions: Apache Flex 4.11.0, Apache Flex 4.12.0, Apache Flex 4.13.0, Apache
Flex 4.12.1
>            Reporter: Vadim Usoltsev
>            Priority: Critical
> Since there is gridView appeared in DataGridSkin the performance of the component is
extremely decreased. By performance I mean update display list operations. At the moment the
overall performance depends on data provider size, but this is contrary to the principle of
the DataGrid when you can display huge amount of data with limited amount of item renderers
> How to reproduce:
> Create s:DataGrid with a few columns, generate dataProvider with objects corresponging
to the columns. For ~500 objects you will already see visible rendering lugs, just move your
mouse over the grid or try to scroll. For ~2000 objects DataGrid becomes totally unusable.
> This behaviour can be reproduced in 4.11-4.13 flex SDK versions, while in 4.5.1 and even
in 4.9.1 everything is Okey.

This message was sent by Atlassian JIRA

View raw message