-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
The rate of effective use of memory is low when doing sst merge, is it right? #49
Comments
Can you elaborate this problem a little bit more? What are the "useless values"? Right now when compacting sst files, we'll not load the whole file; instead, we'll read 1 block (by default it is 4k) to the memory. |
Is there an option to use madvise for those reads? On Thu, Jan 2, 2014 at 10:50 AM, Kai Liu notifications@github.com wrote:
Mark Callaghan |
use util.inherits() from node core
use more efficient emptiness checking
the whole sst file must be loaded when doing sst merge, some useless value will be read into memory repeatedly, a lot of useless values can cost much memory,is it right?
The text was updated successfully, but these errors were encountered: