News for hackers. Stuff that matters.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by umanwizard on Friday June 06, 2025 @12:23PM (#44202436)
This is not the precise mathematical definition of exponential, but rather the colloquial one, where it just means "a lot".
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by cvoss on Friday June 06, 2025 @02:23PM (#44203603)
You shouldn't use a word that can carry a precise mathematical meaning in a sentence that literally uses mathematical notation in order to speak precisely and then expect readers not to interpret the word in the precise mathematical way.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by blharr on Friday June 06, 2025 @03:22PM (#44204095)
I somewhat agree, but for lack of a better word, what would you use? Quadratically doesn't have the same punch
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by umanwizard on Friday June 06, 2025 @03:31PM (#44204189)
“Dramatically” ?
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by remram on Friday June 06, 2025 @05:06PM (#44204991)
"a lot"
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by jjmarr on Friday June 06, 2025 @05:21PM (#44205109)
"by a factor of `n`" also sounds impressive.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by jrochkind1 on Friday June 06, 2025 @06:29PM (#44205652)
If you just mean "a lot" in a non-technical sense, there are plenty of words available. enormously. immensely. tremendously. remarkably. incredibly. vastly.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by bobbylarrybobby on Friday June 06, 2025 @10:51PM (#44207029)
“From quadratic to linear” seems fine.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by bobbylarrybobby on Friday June 06, 2025 @10:51PM (#44207032)
“From quadratic to linear” or “... to constant” seems fine.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by morepedantic on Saturday June 07, 2025 @02:49AM (#44207924)
Algorithmic? Big-O? Polynomially? Linear improvement? O(n^2) to O(n)? Or if you want to be less mathematically precise: enormous improvement?

Using exponential in this way in any context is a faux pas, because it's highly ambiguous, and requires context for clarification. But in this situation the context clearly resolved to the mathematically accurate definition, except it was used in the other way.

Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by globular-toast on Saturday June 07, 2025 @03:28AM (#44208064)
Runtimes dropped precipitously.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by ndriscoll on Saturday June 07, 2025 @07:59AM (#44209073)
Quadratically doesn't have the same punch because it is actually exponentially less than exponentially. So doing it for extra punch (as opposed to not knowing the correct word) in a technical context would just be lying. It'd be like a paper saying they had a result with p less than one in a trillion for "extra punch" when they actually had p=0.1.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by IshKebab on Friday June 06, 2025 @03:25PM (#44204120)
You should if you expect your readers to be normal humans who understand obvious context, and not pedantic HN readers who understand obvious context but delight in nit-picking it anyway.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by Dylan16807 on Friday June 06, 2025 @05:26PM (#44205154)
You can, but it's not should.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by morepedantic on Saturday June 07, 2025 @02:45AM (#44207910)
>pedantic

Who the fuck do you think is the intended audience for an article about an algorithm in `git bundle create`? I spent approximately two minutes of my life trying to figure out where the O(n^2) algorithm was being invoked in such a way that it influenced an exponential.

Exponential was bolded in the same sentence as a big-O. 50/50 troll/author oversight.

Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by saagarjha on Saturday June 07, 2025 @07:08AM (#44208866)
Maybe not 'morepedantic
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by globular-toast on Saturday June 07, 2025 @03:25AM (#44208057)
Ah yes because "normal humans" know what O(n^2) means but damnit they are going to use exponential wrong.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by tomjakubowski on Sunday June 08, 2025 @12:33PM (#44217961)
I'm a normal human and I know what O(n^2) means. There are dozens of us.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by sneak on Friday June 06, 2025 @05:19PM (#44205091)
“Words mean things.”

If you can’t agree with this, then you shouldn’t be speaking or writing, IMO.

Those who argue that words that mean different things are actually equivalent have no business dealing with language.

Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by morepedantic on Saturday June 07, 2025 @02:51AM (#44207932)
I understood every word, phrase, and sentence you wrote. But I did not understand your point. Still, I got the meaning of your words, so presumably you're satisfied.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by hskalin on Friday June 06, 2025 @11:34PM (#44207221)
I find the whole article rather poorly written. Most likely using an LLM.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by morepedantic on Saturday June 07, 2025 @02:42AM (#44207894)
Especially when the colloquial meaning derives from the mathematical meaning.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by MyFedora on Saturday June 07, 2025 @06:18AM (#44208681)
We simplify the big O notation in computer science. This is standard practice.
Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by rovr138 on Saturday June 07, 2025 @09:38AM (#44209586)
Just drop the constants, it doesn't matter /s

Production systems running and melting here...

Re:Decreasing Gitlab repo backup times from 48 hours to 41 m... by morepedantic on Saturday June 07, 2025 @02:41AM (#44207891)
>Ultimately, 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.

No, not in the exact same sentence as a big-O. That's either author error, or an intentional troll. Either way it's egg on their faces.