-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lz4 compression while building totals
is resource intensive
#18
Labels
Comments
Also, there seems to be problems with Node.js 10.x compat for |
Seems to be a problem on This does not cause high memory load: const outstream = fs.createWriteStream(`${file}.gz`);
const passThrough = new stream.PassThrough();
const gzip = zlib.createGzip({ level: 1 });
passThrough.pipe(gzip).pipe(outstream);
return passThrough; This causes high memory load: const outstream = fs.createWriteStream(`${file}.lz4`);
const encoder = lz4.createEncoderStream({ highCompression: false });
encoder.pipe(outstream);
return encoder; lz4 is significantly faster than gzip though. |
This was referenced Jul 25, 2018
Closed
Blocked against nodejs/node#21967. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This needs investigation, but something looks wrong with lz4-compressed streams while
gzemnid extract totals
is running — the app consumes all the available memory and crashes.Disabling the compression in
config.local.json
and compressing those files manually with command-line stand-alonelz4
works and can be used as a work-around.The text was updated successfully, but these errors were encountered: