GitHub user 2ooom opened a pull request:

    [SPARK-21254] [WebUI] History UI performance fixes 

    ## This is a backport of PR #18783 to the latest released branch 2.2.  
    ## What changes were proposed in this pull request?
    As described in JIRA ticket, History page is taking ~1min to load for cases 
when amount of jobs is 10k+.
    Most of the time is currently being spent on DOM manipulations and all 
additional costs implied by this (browser repaints and reflows).
    PR's goal is not to change any behavior but to optimize time of History UI 
    1. The most costly operation is setting `innerHTML` for `duration` column 
within a loop, which is [extremely 
 this helped to get page load time **down to 10-15s**
    2. Second big gain bringing page load time **down to 4s** was [was 
 by detaching table's DOM before parsing it with DataTables jQuery plugin.
    3. Another chunk of improvements 
 was focused on removing unnecessary DOM manipulations that in total 
contributed ~250ms to page load time.
    ## How was this patch tested?
    Tested by existing Selenium tests in 
    Changes were also tested on Criteo's spark-2.1 fork with 20k+ number of 
rows in the table, reducing load time to 4s.

You can merge this pull request into a Git repository by running:

    $ git pull history-ui-perf-fix-2.2

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #18860
commit b7e56eef4d66af977bd05af58a81e14faf33c211
Author: Dmitry Parfenchik <>
Date:   2017-06-05T20:42:41Z

    [SPARK-21254] [WebUI] History UI: Improving performance by detaching table 
DOM before processing
    Currently all the DOM manipulations are handled in a loop after Mustache
    template is parsed. This causes severe performance issues especially within
    loops iteration over thousands of (attempt/application) records and causing
    all kinds of unnecessary browser work: reflow, repaint, etc.
    This could be easily fixed by preparing a DOM node beforehand and doing all
    manipulations within the loops on detached node, reattaching it to the 
    only after the work is done.
    The most costly operation in this case was setting innerHTML for `duration`
    column within a loop, which is extremely unperformant:
    While duration parsing could be done before mustache-template processing 
    any additional DOM alteratoins.

commit aeeeeb520d156a7293a707aa6bc053a2f83b9ac2
Author: Dmitry Parfenchik <>
Date:   2017-07-30T14:52:24Z

    [SPARK-21254] [WebUI] Performance optimization for pagination check
    Check whether to display pagination or not on large data sets (10-20k rows)
    was taking up to 50ms because it was iterating over all rows. This could be
    easily done by testing length of array before passing it to mustache.

commit e25be9a66b018ba0cc53884f242469b515cb2bf4
Author: Dmitry Parfenchik <>
Date:   2017-07-30T15:23:37Z

    [SPARK-21254] [WebUI] Performance improvement: removing unnecessary DOM 
    Logic related to `hasMultipleAttempts` flag:
     - Hiding attmptId column (if `hasMultipleAttempts = false`)
     - Seting white background color for first 2 columns (if 
`hasMultipleAttempts = true`)
    was updating DOM after mustache template processing, which was causing 2 
    iterations over full data set (first through jquery selector, than through 
    Refactoring it inside mustache template helps saving 80-90ms on large data 
sets (10k+ rows)

commit 91697079a29138b7581e64f2aa79247fa1a4e4af
Author: Dmitry Parfenchik <>
Date:   2017-07-30T20:06:32Z

    [SPARK-21254] [WebUI] Performance improvement: further reducing DOM 
    Refactoring incomplete requests filter behavior due to inefficency in DOM
    manipulations. We were traversing DOM 2 more times just to hide columns
    that we could have avoided rendering in mustache. Factoring this logic in
    mustache template (`showCompletedColumn`) saves 70-80ms on 10k+ rows.

commit 3630ca212baa94d60c5fe7e4109cf6da26288cec
Author: Dmitry Parfenchik <>
Date:   2017-07-30T20:26:59Z

    [SPARK-21254] [WebUI] Performance improvements: detaching DOM before 
DataTables plugin processing
    Detaching history table wrapper from document before parsing it with 
DataTables plugin
    and reattaching back right after plugin has processed nested DOM. This 
allows to avoid
    huge amount of browser repaints and reflows, reducing initial page load 
time in Chrome
    from 15s to 4s for 20k+ rows


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to