-
Notifications
You must be signed in to change notification settings - Fork 178
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
Use disk option(s) #75
Labels
Comments
Please try |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get why everything happens in memory, but sometimes you just cannot fit your whole test file into it.
Or maybe you can, but it's the combined size with the RAM requirements of the most "hungry compressors" to make it a bad day for you.
Or even, you could, but the "clue" you are looking for happens below the bandwidth threshold of your non volatile memory.
So, putting aside that it I/O bottlenecks could be detected and flagged (I suppose it may also be true for RAM in some crazy situation?), could we get some kind of knob to control the "disk type"?
I see three possible levels for this:
The text was updated successfully, but these errors were encountered: