[
https://issues.apache.org/jira/browse/MAPREDUCE-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492571#comment-13492571
]
Ravi Prakash commented on MAPREDUCE-4720:
-----------------------------------------
Hi Luke!
For 20000 jobs
$ time curl localhost:19888/jobhistory > file
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3812k 0 3812k 0 0 26.3M 0 --:--:-- --:--:-- --:--:-- 26.5M
real 0m0.147s
user 0m0.002s
sys 0m0.017s
For 200000 jobs
$ time curl localhost:19888/jobhistory > file
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 37.5M 0 37.5M 0 0 9332k 0 --:--:-- 0:00:04 --:--:-- 9346k
real 0m4.151s
user 0m0.022s
sys 0m0.098s
So I doubt that the Jetty server is having trouble streaming the data.
> Browser thinks History Server main page JS is taking too long
> -------------------------------------------------------------
>
> Key: MAPREDUCE-4720
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4720
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.3
> Reporter: Robert Joseph Evans
> Assignee: Ravi Prakash
> Attachments: MAPREDUCE-4720.patch, MAPREDUCE-4720.patch
>
>
> The main History Server page with the default settings of 20,000 jobs can
> cause browsers to think that the JS on the page is stuck and ask you if you
> want to kill it. This is a big usability problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
