Hi John,

I'm currently working on FastBit support for compressed files. To simplify
things a bit for a start, I have disabled the MMAP support and forced
FastBit to use open, read, write and seek functions. Then I hooked into
these functions and provided a compression layer. The problem is that just
disabling the MMAP causes FastBit to use so much memory that OOM killer
terminates the process for some aggregation queries.

Is there anything I can do to tell FastBit to limit the amount of memory it
can use? I thought that only half of the available memory will be used by
default. I've tested this issue on latest SVN revision.

Thank you in advance for any help,
Petr Velan
_______________________________________________
FastBit-users mailing list
[email protected]
https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users

Reply via email to