[ https://issues.apache.org/jira/browse/SPARK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052289#comment-14052289 ]
Mridul Muralidharan commented on SPARK-2017: -------------------------------------------- With aggregated metrics, we loose the ability to check for gc time (which is actually what I use that UI for, other than to dig up exceptions on failed tasks). > web ui stage page becomes unresponsive when the number of tasks is large > ------------------------------------------------------------------------ > > Key: SPARK-2017 > URL: https://issues.apache.org/jira/browse/SPARK-2017 > Project: Spark > Issue Type: Sub-task > Reporter: Reynold Xin > Labels: starter > > {code} > sc.parallelize(1 to 1000000, 1000000).count() > {code} > The above code creates one million tasks to be executed. The stage detail web > ui page takes forever to load (if it ever completes). > There are again a few different alternatives: > 0. Limit the number of tasks we show. > 1. Pagination > 2. By default only show the aggregate metrics and failed tasks, and hide the > successful ones. -- This message was sent by Atlassian JIRA (v6.2#6252)