[
https://issues.apache.org/jira/browse/YARN-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503294#comment-14503294
]
Ravi Prakash commented on YARN-3500:
------------------------------------
We have gone back and forth on paging server side and client side. The earlier
UI used to be paged server side. For some reason, paging was moved to client
side. One of them was that even for 10k jobs, the amount of JSON data was
pretty small. [~shihaoliang] Have you profiled where those 55 seconds were
spent? How much of that was network transfer?
Personally I like server side paging, specially if we default to showing a LOT
of jobs. I'd be in favor of [Server-side
Datatables|https://www.datatables.net/examples/data_sources/server_side.html]
(but it may require a lot of effort).
> Optimize ResourceManager Web loading speed
> ------------------------------------------
>
> Key: YARN-3500
> URL: https://issues.apache.org/jira/browse/YARN-3500
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Reporter: Peter Shi
>
> after running 10k jobs, resoucemanager webui load speed become slow. As
> server side send 10k jobs information in one response, parsing and rendering
> page will cost a long time. Current paging logic is done in browser side.
> This issue makes server side to do the paging logic, so that the loading will
> be fast.
> Loading 10k jobs costs 55 sec. loading 2k costs 7 sec
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
