1095213 - Do not load all job data unconditionally

Status: RESOLVED DUPLICATE of bug 1107667

(Tree Management :: Treeherder, defect, P2)

Description

[Steve Fink [:sfink] [:s:]]

I often want to browse back in the pushlog to an older push and see the pushes around it. Right now, that is a very mean thing to do to treeherder. You have to click the "10/20/50" buttons until you find the one you want, which means you're loading a metric ton of job result data that you don't care about. In this case, I would prefer if it did not initially load the job data until I asked for a push to be expanded. I suppose it could load the data for the initial page, but then when I clicked on the 50 button it wouldn't load the data for those pushes unless requested.

I suspect there are a number of other situations where the data isn't needed and will be ignored, wasting time and resources.

Comment 1

[Ed Morley [:emorley]]

Perhaps we could make new pushes be collapsed and only partially loaded by default, if the number of visible pushes exceeds N.

Alternatively we could try an idea that was suggested in Portland - using a fixed pagination size and having the older/newer links scroll through the pushes, never displaying more than the pagination size (user adjustable). 

Would the latter solve your use case?

Comment 3

[Ed Morley [:emorley]]

(In reply to Ed Morley [:edmorley] from comment #1)
> Alternatively we could try an idea that was suggested in Portland - using a
> fixed pagination size and having the older/newer links scroll through the
> pushes, never displaying more than the pagination size (user adjustable). 
> 
> Would the latter solve your use case?

Ah just found bug 1107667 is filed for it.