Closed peczenyj closed 10 years ago
@peczenyj This is an unfortunate naming overlap. When you specify "in_memory" in the create statement, it controls if the filter exists only in memory, meaning it is not persisted to disk. By default it is 0, meaning it is saved to disk.
When you do info
on a filter, it returns various stats. The in_memory
key represents if the filter is currently located in-memory, not if it is only in memory. Does that distinction make sense?
A filter that is in-memory only will never be faulted to disk, since there is no persistent representation. Normal filters will be removed from memory after a period of inactivity, and thus they will report "in_memory 0".
running bloomd with default options
I am setting in_memory to 0, then
seems bloomd is ignoring the in_memory option. why?