[
https://issues.apache.org/jira/browse/FLINK-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323608#comment-17323608
]
Flink Jira Bot commented on FLINK-7607:
---------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Web Frontend Hangs with Large Numbers of Tasks
> ----------------------------------------------
>
> Key: FLINK-7607
> URL: https://issues.apache.org/jira/browse/FLINK-7607
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Web Frontend
> Affects Versions: 1.3.2
> Environment: Attempted to load the web frontend on a MacBook Pro 15"
> (late 2016) with 16 GB of memory using both Chrome 60.0 and Safari 10.1.2.
> Reporter: Joshua Griffith
> Assignee: Steven Langbroek
> Priority: Major
> Labels: performance, stale-assigned
>
> Viewing a job with a high number of tasks in the web front-end causes the
> page to hang, consuming 100% CPU on a core. At 200 tasks the page slows
> noticeably and scrolling results in long, non-responsive pauses. At 400 tasks
> the page only updates once per minute and is almost entirely non-responsive.
> Initially, I thought this was caused by rendering a complex job graph but
> opening the inspector and deleting the canvas did not improve page
> performance. Further inspection indicated that the page was redrawing every
> DOM element in the task list on every update.
> A possible solution is to use an approach similar to
> [react-list|https://github.com/orgsync/react-list] and only request
> data/render list items that are in view and only update DOM nodes that have
> changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
