npm feed + nodejs.org connector: huge memory footprint and npm install ECONNRESETs

enrico+proget_8830

hi

we see a huge memory footprint on our proget installation when populating the npm feed + connector cache. once populated we see frequent ECONNRESET during 'npm ci' runs.

for resource footprint reason we switched to verdaccio to serve as our npm cache. though, we also see ECONNRESETs there.

some specs:
1 - during cache population we have a 4 cpu + 30 gb ecs service with 3 tasks hosting nginx, proget and mssql
2 - once the cache is populated we have a 2 cpu + 5 gb ecs service (same tasks)
3 - package.json resolve to 1500-2500 dependencies which hold about 1.5-2gb on node_modules
4 - 4-5 simultaneous 'npm ci' processes run against the ecs cluster (with local cache cleaned and removed node_modules directory)
5 - to compare - the same cache population works on a verdaccio ecs service (2 tasks hosting nginx, verdaccio) with 2gb ram (ignore the fact it does not need mssql - on proget, mssql plays a minimal role on resources footprint)

is the footprint expected ? how to overcome the ECONNRESET issue ?

any ideas ?

thank you

rhessinger

Hi @enrico-proget_8830,

Can you please tell me which version of ProGet you are running?

Thanks,
Rich

gcoric

It's 24.0.22.5 according to our records

-Gene

rhessinger

Hi @enrico-proget_8830,

So we have fixed multiple issues with npm, specifically the npm connectors in the versions since you installed. I think upgrading to ProGet 2025.26 should resolve your issue with the ECONNRESET issue. Could you update to 2025.26 and rerun your test and let us know if you are still seeing the issue?

Here is a link to the change list since your version of ProGet: https://my.inedo.com/downloads/upgrade?product=ProGet&fromVersion=2024.22

Thanks,
Rich