We have to manage a handful of rather big Git repositories (>1GiB, don't ask), which our untuned test-instance of Kallithea handles just fine - with one exception: displaying big changesets in the browser.
Kallithea warns about this (after a minute or so of occasionaly heavy CPU usage): "Changeset was too big and was cut off... ", but leaves the option to "Show full diff anyway", which in our case leads to more heavy CPU usage and out-of-memory-errors sooner or later.
This enables users only having read access to easily bring our server to its knees.
I'd argue that there is no common use case requiring to display gigabytes of diff in the Browser. Would it be sensible to add an option that disables showing the full diff (or otherwise handle this more gracefully)? Or is this just a misconfiguration on my part?