Details
-
Question
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
Description
Hello, we have a couple of questions that we were hoping that you could answer.
Our use case is using MongoDB as both a message queue as well as a message store. The data in the message queue needs to be fast to access and fast to update while the data in the message store will require lots of space but gets accessed infrequently. They should all be accessible in the same mongo application as well to avoid having to reference two separate instances as it might be just as easy to use a database as the message store. So given the use case above, here are the questions:
1) How does the mechanism work that determines what documents should be kept in RAM when mongo exceeds the size of the machine's physical RAM rather than disk?
2) Can we leverage a configuration setting or some detail about the aforementioned mechanism to ensure that using the same mongo application as a message store will not impact the performance of the message queue?
Thanks in advance.