hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4720) Browser thinks History Server main page JS is taking too long
Date Tue, 06 Nov 2012 18:36:12 GMT

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

Ravi Prakash updated MAPREDUCE-4720:

    Attachment: MAPREDUCE-4720.patch

Thanks for that Luke! I *had* updated it in a separate branch and forgot to include it in
the patch. Here's the whole branch. I generated this patch using git diff --binary --no-prefix
--full-index . I have yet to figure out how to apply this using patch.

Nathan had suggested me to use YSlow and fix the bad grade it gave. I put in a few improvements:
1. Combined multiple Javascript files so that fewer HTTP connections are opened.
2. Static content is being sent with the "Expires" header set to an year from when the request
is made.
3. Datatables upgraded and deferred rendering.

Its taking about 8 seconds to render the 20000 fake jobs. An improvement from 11 seconds but
still leaves something to be desired.

1. Should I combine all the JS files? Or only the well known jquery, jquery-ui and jquery-datatables
2. Should I version the static directory? I didn't feel the need because a refresh on the
client browser can be made to refetch the un-expired content anyway.
3. Is there anything else we should be doing?
> 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

View raw message