How we decreased GitLab repo backup times from 48 hours to 41 minutes
1–10 of 273 posts
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#2Quadratic complexity sits in an awkward sweet spot: Fast enough for medium-sized n to pass first QA, but doomed to fail eventually as n grows.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#3Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#4Are there any reimplementations of git, by professional programmers using real tools? The source in question — object.c — is "banging rocks together" material.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#5See also: https://www.tumblr.com/accidentallyquadratic Quadratic complexity sits in an awkward sweet spot: Fast enough for medium-sized n to pass first QA, but doomed to fail eventually as n grows.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#6If the backup times were O(n^2), are they now O(n^2 / 2^n)? I would guess not.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#7Are there any reimplementations of git, by professional programmers using real tools? The source in question — object.c — is "banging rocks together" material.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#8"fixed it with an algorithmic change, reducing backup times exponentially" If the backup times were O(n^2), are they now O(n^2 / 2^n)? I would guess not.
Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#9Re: How we decreased GitLab repo backup times from 48 hours to 41 minutes
#10"fixed it with an algorithmic change, reducing backup times exponentially" If the backup times were O(n^2), are they now O(n^2 / 2^n)? I would guess not.