flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wenjie Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-32608) Performance problem with bubble charts with large number of items
Date Wed, 05 Feb 2014 20:50:10 GMT

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

Wenjie Zhang commented on FLEX-32608:
-------------------------------------

Any update for this bug? I got the same issue, but for my use case, the chart gets slow when
There are more then 8000 items.

> Performance problem with bubble charts with large number of items
> -----------------------------------------------------------------
>
>                 Key: FLEX-32608
>                 URL: https://issues.apache.org/jira/browse/FLEX-32608
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Charts
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): Windows
> Affected OS(s): Windows XP
> Language Found: English
>            Reporter: Adobe JIRA
>
> There are around 2000 bubbles in the chart. This app has feature of drawing rectangle
on the chart to select, zoom or pan the map using the mouse. All code included.  It seems
like when a mouse is moved all the items in the chart are getting rendered. The performance
is sluggish and response is slow.
> Steps to reproduce:
>    
>     Create a project with given files and run the app.
>  
>  Actual Results:
>      as you move the mouse around in the chart area, the crosshair is drawn very slowly
and the CPU goes to 100%. the app becomes unresponsive and unusable
>      
>  Expected Results:
>     the app should be usable. Any workarounds to turn the rendering of the bubble chart
off?. any other recommended ways to draw rectangles or doing pans on the charts?. The performance
starts suffering with as little as 1000 items.
>  
>  
>  Workaround (if any):



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message