nodejs / nodejs/build

Inconsistent slow downloads from nodejs.org

Open
#3,853 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jinja
Stars
541
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

I am not sure if nodejs/build is the right place to file, so feel free to move

When trying to download a nodejs version, we usually are very fast. We see similar speeds from our CI servers, local, etc across multiple networks

Example:

> curl https://nodejs.org/dist/v20.16.0/node-v20.16.0-linux-x64.tar.gz --output a.tar.gz

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 44.5M  100 44.5M    0     0  10.7M      0  0:00:04  0:00:04 --:--:-- 10.7M

However, at random times, we get super slow. I can rerun this download 10 times, and 3 will fail with this slowness

it's not a local network issue, as this is happening across multiple networks and people, and appears worse over the last 3 days.

Any insight or additional info I can provide support for?

Example - before I killed it 6 minutes in - 152K download:

> curl https://nodejs.org/dist/v20.16.0/node-v20.16.0-linux-x64.tar.gz --output a.tar.gz

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 87 44.5M   87 38.8M    0     0   102k      0  0:07:27  0:06:30  0:00:57  152k^C

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the nodejs/build repository and reproduce the curl request for the nodejs.org distribution URL shown in the report across the affected networks. Investigate the download path and build infrastructure involved; done means identifying the source of the intermittent slowdown and documenting a verified resolution or next diagnostic step.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
infrastructure, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.