Description
Since a long time ago my team/company suffered from history server being very slow to display/search entries specially when entries grow over 50k entry, regardless there is a pagination there in that page already but still very slow to display the entries.
Current situation Mustache Js is used to render the entries and datatables is used to manipulate it (sort by column and search).
By getting rid of Mustache (stop rendering the entries using Mustache) and using datatables to display it proved to be faster.
Displaying > 100k entries (my case):
Existing takes at least 30 to 40 seconds to display the entries, searching takes at least 20 seconds and the page stop responding until it finishes.
Improved takes ~3 seconds to display the entries searching is very fast and the page stays responsive.
(These numbers will be different for others since JS is executed on your browser)
I am not sure why Mustache is used to display the data since data tables can do the job,
ajbozarth sowen please elaborate more about this what is the reason to use Mustache? what are the drawbacks if it's not used anymore to display the entries (only this part)?
Attachments
Attachments
Issue Links
- causes
-
SPARK-45749 Fix Spark History Server to sort `Duration` column properly
-
- Resolved
-
- links to
