News for hackers. Stuff that matters.
Re:My failed attempt to shrink all NPM packages by 5% by pif on Monday January 27, 2025 @09:57AM (#42841748)
> This is a solid example of how things change at scale.

5% is 5% at any scale.

Re:My failed attempt to shrink all NPM packages by 5% by michaelmior on Monday January 27, 2025 @10:26AM (#42842076)
Yes and no. If I'm paying $5 a month for storage, I probably don't care about saving 5% of my storage costs. If I'm paying $50,000/month in storage costs, 5% savings is a lot more worthwhile to pursue
Re:My failed attempt to shrink all NPM packages by 5% by PaulHoule on Monday January 27, 2025 @10:39AM (#42842239)
Doesn't npm belong to Microsoft? It must be hosted in Azure which they own so they must be paying a rock bottom rate for storage, bandwidth, everything.
Re:My failed attempt to shrink all NPM packages by 5% by cwmma on Monday January 27, 2025 @10:58AM (#42842448)
It's probably less about MS and more about the people downloading the packages
Re:My failed attempt to shrink all NPM packages by 5% by PaulHoule on Monday January 27, 2025 @11:29AM (#42842823)
For them it is 5% of something tiny.
Re:My failed attempt to shrink all NPM packages by 5% by imoverclocked on Monday January 27, 2025 @01:27PM (#42844082)
Maybe, maybe not. If you are on a bandwidth limited connection and you have a bunch of NPM packages to install, 5% of an hour is a few minutes saved. It's likely more than that because long-transfers often need to be restarted.
Re:My failed attempt to shrink all NPM packages by 5% by PaulHoule on Monday January 27, 2025 @01:43PM (#42844254)
A properly working cache and download manager that supports resume goes a long way.

I could never get Docker to work on my ADSL when it was 2 Mbps (FTTN got it up to 20) though it was fine in the Montreal office which had gigabit.

Re:My failed attempt to shrink all NPM packages by 5% by sneak on Monday January 27, 2025 @11:48PM (#42848938)
The amount of modules my docker hosts download from npm is anything but tiny.
Re:My failed attempt to shrink all NPM packages by 5% by horsawlarway on Monday January 27, 2025 @11:08AM (#42842571)
5% of newly published packages, with a potentially serious degradation to package publish times for those who have to do that step.

Given his numbers, let's say he saves 100Tb of bandwidth over a year. At AWS egress pricing... that's $5,000 total saved.

And arguably - NPM is getting at least some of that savings by adding CPU costs to publishers at package time.

Feels like... not enough to warrant a risky ecosystem change to me.

Re:My failed attempt to shrink all NPM packages by 5% by true_religion on Monday January 27, 2025 @12:13PM (#42843310)
[delayed]
Re:My failed attempt to shrink all NPM packages by 5% by canucker2016 on Monday January 27, 2025 @04:59PM (#42846180)
In a great example of the Pareto Principle (80/20), or actually even more extreme, let's only apply this Zopfli optimization if the package download total is equal or more than 1GiB (from the Weekly Traffic in GiB column of the Top 5000 Weekly by Traffic tab of the Google Sheets file from the reddit post).

For reference, total bandwidth used by all 5000 packages is 4_752_397 GiB.

Packages >= 1GiB bandwidth/week - That turns out to be 437 packages (there's a header row, so it's rows 2-438) which uses 4_205_510 GiB.

So 88% of the top 5000 bandwidth is consumed by downloading the top 8.7% (437) packages.

5% is about 210 TiB.

Limiting to the top 100 packages by bandwidth results in 3_217_584 GiB, which is 68% of total bandwidth used by 2% of the total packages.

5% is about 161 TiB.

Re:My failed attempt to shrink all NPM packages by 5% by canucker2016 on Monday January 27, 2025 @06:21PM (#42847001)
Packages with >= 20GiB bandwidth == 47 packages totaling 2,536,902.81 GiB/week.

Less than 1% of top 5000 packages took 53% of the bandwidth.

5% would be about 127 TiB (rounded up).

Re:My failed attempt to shrink all NPM packages by 5% by AlotOfReading on Monday January 27, 2025 @11:43AM (#42842982)
How often are individuals publishing to NPM? Once a day at most, more typically once a week or month? A few dozen seconds of one person's day every month isn't a terrible trade-off.

Even that's addressable though if there's motivation, since something like transcoding server side during publication just for popular packages would probably get 80% of the benefit with no client-side increase in publication time.

Re:My failed attempt to shrink all NPM packages by 5% by gregmac on Monday January 27, 2025 @10:35AM (#42842196)
5% off your next lunch and 5% off your next car are very much not the same thing.
Re:My failed attempt to shrink all NPM packages by 5% by dgfitz on Monday January 27, 2025 @12:43PM (#42843638)
So what, instead of 50k for a car you spend 47.5k?

If that moves the needle on your ability to purchase the car, you probably shouldn't be buying it.

5% is 5%.

Re:My failed attempt to shrink all NPM packages by 5% by kemitche on Monday January 27, 2025 @01:34PM (#42844163)
If it takes 1 hour of effort to save 5%:

- Doing 1 hour of effort to save 5% on your $20 lunch is foolhardy for most people. $1/hr is well below US minimum wage. - Doing 1 hour of effort to save 5% on your $50k car is wise. $2500/hr is well above what most people are making at work.

It's not about whether the $2500 affects my ability to buy the car. It's about whether the time it takes me to save that 5% ends up being worthwhile to me given the actual amount saved.

The question is really "given the person-hours it takes to apply the savings, and the real value of the savings, is the savings worth the person-hours spent?"

Re:My failed attempt to shrink all NPM packages by 5% by jay_kyburz on Monday January 27, 2025 @03:25PM (#42845233)
This is something we often do in our house. We talk about things in terms of hours worked rather than price. I think more people should do it.
Re:My failed attempt to shrink all NPM packages by 5% by dgfitz on Monday January 27, 2025 @07:43PM (#42847624)
By that logic I waste time reading books instead of paying someone else to read them for me.
Re:My failed attempt to shrink all NPM packages by 5% by viceroyalbean on Monday January 27, 2025 @08:57PM (#42848083)
If you can get the exact same result for less cost (time and money), why not? Things like enjoyment don't factor in since they can't be directly converted into money.
Re:My failed attempt to shrink all NPM packages by 5% by jay_kyburz on Monday January 27, 2025 @10:46PM (#42848630)
Paying somebody else to read the book means you don't get the benefit of the book.

Also, this is exactly what you company is doing, paying you to "read the book" so they don't have to.

Re:My failed attempt to shrink all NPM packages by 5% by ziddoap on Monday January 27, 2025 @12:56PM (#42843776)
Why do so many people take illustrative examples literally?

I'm sure you can use your imagination to substitute "lunch" and "car" with other examples where the absolute change makes a difference despite the percent change being the same.

Even taking it literally... The 5% might not tip the scale of whether or not I can purchase the car, but I'll spend a few hours of my time comparing prices at different dealers to save $2500. Most people would consider it dumb if you didn't shop around when making a large purchase.

On the other hand, I'm not going to spend a few hours of my time at lunch so that I can save an extra $1 on a meal.

Re:My failed attempt to shrink all NPM packages by 5% by post-it on Monday January 27, 2025 @12:49PM (#42843686)
I wouldn't pick 5¢ up off the ground but I would certainly pick up $2500.
Re:My failed attempt to shrink all NPM packages by 5% by ggm on Monday January 27, 2025 @09:59PM (#42848415)
You'd keep 5c. A significant number of people who find sums up around $2500 give it back unconditionally, with no expectation of reward. Whoever lost $2500 is having a really bad day.
Re:My failed attempt to shrink all NPM packages by 5% by JZerf on Monday January 27, 2025 @12:54PM (#42843740)
Those lunches could add up to something significant over time. If you're paying $10 per lunch for 10 years, that's $36,500 which is pretty comparable to the cost of a car.
Re:My failed attempt to shrink all NPM packages by 5% by Julien_r2 on Monday January 27, 2025 @06:40PM (#42847162)
Which is, then, supporting the fact that scale matter, isn't it?

Here the scale of time is larger and does make the 5$ significant, while it isn't at the scale of a few days.

Re:My failed attempt to shrink all NPM packages by 5% by knighthack on Monday January 27, 2025 @11:29AM (#42842815)
Do you even know how absolute numbers work vis-à-vis percentages?
Re:My failed attempt to shrink all NPM packages by 5% by Aicy on Monday January 27, 2025 @12:36PM (#42843565)
That's right, and 5% of a very small number is a very small number. 5% of a very big number is a big number.
Re:My failed attempt to shrink all NPM packages by 5% by syncsynchalt on Monday January 27, 2025 @12:50PM (#42843705)
In some scenarios the equation flips, and the enterprise is looking for _more_ scale.

The more bandwidth that Cloudflare needs, the more leverage they have at the peering table. As GitHub's largest repo (the @types / DefinitelyTyped repo owned by Microsoft) gets larger, the more experience the owner of GitHub (also Microsoft) gets in hosting the world's largest git repos.

I would say this qualifies as one of those cases, as npmjs is hosted on Azure. The more resources that NPM needs, the more Microsoft can build towards parity with AWS's footprint.