Opened 6 years ago

Last modified 4 years ago

#2268 new task

Grid display is very slow when there is lots of history, and multple projects.

Reported by: tom.prince Owned by:
Priority: major Milestone: 0.8.x
Version: 0.8.2 Keywords: web
Cc: rutsky.vladimir@…

Description (last modified by dustin)

The grid displays can be *very* slow, if you are dispaying builds from multiple projects. grid shows the latest build for the most recent sourcestamps. And if some builders don't have *any* builds for some sourcestamps, builtbot needs to read *all* of the buidls for that builder to learn there are no interesting ones. (This is true at least for 0.8.2, but I don't think there have been any relevant changes here).

Change History (6)

comment:1 Changed 6 years ago by dustin

  • Milestone changed from undecided to 0.9.0

I'm not sure there's much to do about this in the 0.8.x series - unless you have some ideas!

comment:2 Changed 6 years ago by tom.prince

The only solution I can think of for 0.8.x is to just limit the number of builds searched to something small. Probably no more that 2-3x the number of builds we want to display in total. If none of the first 20 builds match any of the 10 most recent source stamps, then it is unlikely that any builds on a given builder match.

I guess we need to be careful if we do this, and only limit it in the case that there are *no* matches. Or something dynamic. (In case somebody forces a particular build a bunch of times, pushing earlier builds out of the window).

comment:3 Changed 5 years ago by rutsky

  • Cc rutsky.vladimir@… added

comment:4 Changed 4 years ago by dustin

  • Description modified (diff)
  • Milestone changed from 0.9.0 to 0.9.+

#2640 should help

comment:5 Changed 4 years ago by dustin

  • Milestone changed from 0.9.+ to 0.8.x (unmaintained)

comment:6 Changed 4 years ago by dustin

  • Milestone changed from 0.8.x (unmaintained) to 0.8.x

Milestone renamed

Note: See TracTickets for help on using tickets.