What grows, and what does not
Your stored history grows for as long as you are with us. Two things could grow with it, and only one of them does.
The Findings page shows the most recent findings, and how long it takes to draw
is set by how many findings are on it — not by how many errors sit behind them.
A project with a decade of errors and a project connected this morning draw the
same page in the same time, given the same number of findings on it.
Why that is not automatic
The Findings page asks one question that could have gone the other way. A finding raised during your first fortnight and released at the end of it tells you whether the error behind it has been seen again since the day it was raised. Answering that means finding the most recent report of that error — and “most recent” is a question you can answer either by reading everything and picking the latest, or by going straight to the latest. Reading everything is the version that gets slower the longer you have been with us, on a page you open every day, forever. So we go straight to it. The answer is identical; what changes is that the work does not grow with the pile it is looking into.It also means the page asks that question once for the whole page rather than once per finding, so
a full page of released findings costs one question and not fifty.
What you should expect
- A Findings page that does not get slower as your history gets longer.
- The same readings either way. A finding that has not been seen again still says so; one that has still names the most recent time it was reported to us.
- No archiving, no retention window, and nothing you have to prune to keep the product quick. Trimming your history to make our page fast would be us charging you for our own problem.