Describe the bug
- Node.js version: v16.13.1
- OS & version: macOS 12.6
When I send many get requests, timeout and response.timings are not working as expected.
Actual behavior
I send around 500 get requests to different urls concurrently by using promise, timings.dns of each request is increasing.
Expected behavior
timings.dns should show actual time.
Code to reproduce
const got = require("got");
console.time('total');
const urlList = [
"https://devblogs.microsoft.com/landingpage/",
"https://it.impress.co.jp/list/feed/rss",
"https://uxmilk.jp/feed",
... more 500 urls
];
const pList = urlList.map(function(url) {
return got(url, {timeout: {request: 60000, }, retry: {limit: 0}}).then((result) => {
const phases = result.timings.phases;
const paheseResult = [url, phases.wait, phases.dns, phases.tcp, phases.tls, phases.request, phases.firstByte, phases.download, phases.total];
console.log(paheseResult.join(","));
}).catch((e) => {
return null;
});
});
Promise.all(pList).then((result) => {
console.timeEnd('total');
}).catch((e) => {
console.log('error: ' + e);
});This is the graph which I made from each url's response.timings.
dns is increasing, so if I set timeout to 30s, most of requests fails.
Sorry if this is my misunderstanding because I'm new to node, thanks in advance!
Checklist
- I have read the documentation.
- I have tried my code with the latest version of Node.js and Got.
sindresorhusΒ /Β got
π Human-friendly and powerful HTTP request library for Node.js
14.3k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too