Skip to content
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

control over write buffering #26

Open
nponeccop opened this issue Aug 8, 2011 · 1 comment
Open

control over write buffering #26

nponeccop opened this issue Aug 8, 2011 · 1 comment

Comments

@nponeccop
Copy link
Contributor

Sometimes it is useful to have large (gigabytes) memory buffers and/or long buffering times (e.g. flush if buffer is full or once an hour). And sometimes data is so important that they must be flushed as soon as possible.

@DavidR91
Copy link

Seconded. Using node-dirty to store data during conversion between two formats (60K records). The write performance is inconsequential so it would have been nice to flush every ~10K records (rather than needing 1.5GB+ RAM during the process)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants