Closed Mark-Simulacrum closed 2 years ago
@bors r+
:pushpin: Commit 795e616e8d311ec2ad6551d362890d3ad48a1bfe has been approved by Mark-Simulacrum
:hourglass: Testing commit 795e616e8d311ec2ad6551d362890d3ad48a1bfe with merge bd39e0b515625f22823fd20b33ec459e8a51fd26...
:sunny: Test successful - checks-actions Approved by: Mark-Simulacrum Pushing bd39e0b515625f22823fd20b33ec459e8a51fd26 to master...
This is a pretty expensive query to compute, and while that could be optimized with some amount of indexing and creative SQL, it's not clear that this table delivers much value to the user. If we wanted to present partial reports, that could be done on a periodic basis (e.g., creating the index.html page every hour) and would seem largely more useful, but I don't see a clear motivation for doing so. Triaging crater runs before they're done is unlikely to be useful.
In the meantime, it's better that the UI loads quickly than that we deliver this data.