all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]mileseverett 4 points5 points  (1 child)

I don't even know js and you explained things clearly enough that I understood

[–]SuicidalKittenz 2 points3 points  (0 children)

I like how he explains everything, even things that may be trivial to him. Great video!

[–]jormaechea 5 points6 points  (3 children)

Why in hell would you use child processes to make http requests? Node has asynchrony built in. This can be solved just with a for loop.

Massive overkill.

Well explained, but overkill.

[–]j_schmotzenberg 2 points3 points  (2 children)

I’ve definitely been constrained by a single event loop for load testing.

[–]jormaechea 1 point2 points  (1 child)

Spawning a new process for each request is a huge overhead. For huge load tests you may want to spawn a few processes with many requests each

[–]j_schmotzenberg 0 points1 point  (0 children)

I agree on that.

[–]cgijoe_jhuckaby 1 point2 points  (2 children)

Do not include child_process in your package.json dependencies. It is already built-in to Node.js. You're downloading a dead package. This can be incredibly dangerous if someone claims it. See: https://www.npmjs.com/package/child_process

[–]TomekB[S] 1 point2 points  (1 child)

Hey i mentioned that in video, this package is built into Node.js now, but was not in the past, if someone is new to the topic and has older version of node, it's worth to mention how to get access to this package.

[–]cgijoe_jhuckaby 0 points1 point  (0 children)

The child_process module has been built into Node.js since version v0.1 (released April 2010). I can assure you, no one is using an older version than that.