Hi,
On 19/06/2026 09:22, Christoph Biedl wrote:
I believe that Salsa is still sending very suboptimal packs over the
network, which are then reused by the local Git.
Possibly that's core.bigFileThreshold, and and among other things it's
also a (mild) DoS protection.
That would be quite consistent with this GitLab change:
[gitlab/gitaly] git: Lower big file threshold to improve memory use and
diff latency (2023)
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/6190
as issues started appeared just as we reached 50MB.
Maybe this is something where the LTS Team can help with, let's wait for the
bookworm LTS handover to take place this week, and I'll try and reach out to
involved teams.
Likely I'm missing something here - in my understanding the obstacles
are, in ascending order:
* Spilt the file and re-create the git history.
* Adjust the tooling.
* Seek consensus on the future workflow.
There was some effort ongoing already, including different repacking
strategies. There are notes from the last LTS meeting:
https://lists.debian.org/debian-lts/2026/06/msg00045.html
I'm currently experimenting with splitting (which may also need to
efficiently preserve the current CVE order), a way to keep working on a
merged file (which seems a requirement from the security team), and
companion splits&rewrites for the ELTS tracker and the cvehist rewrite.
Cheers!
Sylvain
