[
https://issues.apache.org/jira/browse/AMBARI-16980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310139#comment-15310139
]
Nitiraj Singh Rathore commented on AMBARI-16980:
------------------------------------------------
I propose the following to make the performance better.
1. the data will continue to be fetched from ATS and DB and merging etc as it
is today.
2. filtering and sorting will continue to be on client side as it is today.
3. (change) only fetching data based on date filter. Only when the date filter
changes the jobs will be refetched, but following points will apply.
4. (new) To show the latest state of the jobs, we will have a polling from
client side for refetching the jobs which are not in terminal state. The
polling interval needs to be decided. This will also be done everytime the
"Refresh" button (new button) is clicked.
5. (new) if the "To Date" is today then we will also periodically fetch the
latest jobs from ATS everytime the user switches from any other tab to history
tab, or when user clicks the "Refresh" button.
6. The initial date filter will be "last 5 days".
> History tab takes long to populate when there is more entry in history table.
> -----------------------------------------------------------------------------
>
> Key: AMBARI-16980
> URL: https://issues.apache.org/jira/browse/AMBARI-16980
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: ambari-2.2.2
> Reporter: Nitiraj Singh Rathore
> Assignee: Nitiraj Singh Rathore
> Fix For: ambari-2.4.0
>
>
> for 638 entries in history table it takes more than 14 seconds to get the
> data from server and populate the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
