Giant changes get a nice shield that says:
This file has a very large number of changes (19,434 lines).
But when this happens, it appears that we're still running pygments over the entire file, only to throw away the results. Can this be avoided? (Right now I'm looking at a diff that takes over a minute to run pygments over.)
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T5644 Add controls to prevent `pygmentize` from saturating system resources | ||
| Resolved | epriestley | T5179 Unearth Differential rendering technical debt | ||
| Duplicate | None | T4988 pygments is run even on very large changesets that won't be shown |
There's some discussion that I'll link up here, but basically the way we degrade large changesets is very coarse and should be much more fine-grained, and include things like this.