184

How GitLab decreased repo backup times from 48 hours to 41 minutes with a fix to Git (about.gitlab.com)

submitted 3 days ago by chaospatterns@lemmy.world to c/programming@programming.dev

25 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] manxu@piefed.social 11 points 2 days ago

we traced the issue to a 15-year-old Git function with O(N²) complexity and fixed it with an algorithmic change, reducing backup times exponentially.

I feel like there is something wrong with this sentence.

[-] drspod@lemmy.ml 8 points 2 days ago

They make the same mistake further down the article:

However, the implementation of the command suffered from poor scalability related to reference count, creating a performance bottleneck. As repositories accumulated more references, processing time increased exponentially.

This article writer really loves bullet point lists, too. 🤨

[-] ugo@feddit.it 8 points 2 days ago* (last edited 2 days ago)

That’s because LLMs really like to output bullet point lists

[-] ulterno@programming.dev -1 points 2 days ago

Welp, guess I am an LLM now :P

load more comments (12 replies)

this post was submitted on 08 Jun 2025

184 points (98.4% liked)

Programming

20767 readers

149 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev