[ 
https://issues.apache.org/jira/browse/SPARK-21254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Parfenchik updated SPARK-21254:
--------------------------------------
    Description: 
Currently on the first page load (if there is no limit set) the whole jobs 
execution history is loaded since the begging of the time. On large amount of 
rows returned (10k+) page load time grows dramatically, causing 1min+ delay in 
Chrome and freezing the process in Firefox, Safari and IE.
A simple inspection in Chrome shows that network is not an issue here and only 
causes a small latency (<1s) while most of the time is spend in UI  processing 
the results according to chrome devtools:
!screenshot-1.png!



  was:
Currently on the first page load (if there is no limit set) the whole jobs 
execution history is loaded since the begging of the time. On large amount of 
rows returned (10k+) page load time grows dramatically, causing 1min+ delay in 
Chrome and freezing the process in Firefox, Safari and IE.
A simple inspection in Chrome shows that network is not an issue here and only 
causes a small latency (<1s) while most of the time is spend in UI  processing 
the results even according to chrome devtools:
!screenshot-1.png!




> History UI: Taking over 1 minute for initial page display
> ---------------------------------------------------------
>
>                 Key: SPARK-21254
>                 URL: https://issues.apache.org/jira/browse/SPARK-21254
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 2.1.0
>            Reporter: Dmitry Parfenchik
>            Priority: Minor
>         Attachments: screenshot-1.png
>
>
> Currently on the first page load (if there is no limit set) the whole jobs 
> execution history is loaded since the begging of the time. On large amount of 
> rows returned (10k+) page load time grows dramatically, causing 1min+ delay 
> in Chrome and freezing the process in Firefox, Safari and IE.
> A simple inspection in Chrome shows that network is not an issue here and 
> only causes a small latency (<1s) while most of the time is spend in UI  
> processing the results according to chrome devtools:
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to