Allow overriding `highWaterMark`
See original GitHub issueFrom what I’ve understood (correct me if I’m wrong) streams in object mode have a default highWaterMark
of 16
which means only 16 vinyl files are processed at a time in parallel.
While 16
is probably a safe default to prevent exhausting the machine resources, it might be good to allow users to override that value for increased performance?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
what is options.highWaterMark? #270 - Blizzard/node-rdkafka
You can override the watermark to change the size of the buffer in your stream.
Read more >Stream | Node.js v19.3.0 Documentation
For streams operating in object mode, the highWaterMark specifies a total number of ... and emitClose options, do not allow the user to...
Read more >node.js - Stream highWaterMark misunderstanding
2) If the highWaterMark limit is reached, the stream cannot buffer anymore, so the #write method returns false to let you know that...
Read more >Set the high watermark - Trellix Product Documentation
Overriding applied protection · How do I override protection? Using updaters · What are updaters? When do I add updaters? What can I...
Read more >Overwriting a data extension with new records - does it affect a ...
Does this matter? High water mark issues? Thoughts here? marketing-cloud · journeybuilder · entry-criteria.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ehmicky this is exceeding the scope of what I’d like to handle here. Maybe if I can start my office hours concept, then we can explore some of those questions more.
No worries I understand. Sorry for going out of the initial scope of the issue.
Just to make the above point clearer, some shell commands only take single file paths as input and don’t handle globbing. I.e. those shell commands need to be repeated/iterated in order to be applied on several files.
One way to do it in a cross-platform way would be to use
Promise.all()
+execa()
. I thought using a stream instead ofPromise.all()
would work just fine as I was not aware of any issues with mixing promises and streams.No need to answer this message if you don’t have the time, I just wanted to make my former message clearer.