Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>MongoDB memory maps the database files. It allows the OS to control this and allocate the maximum amount of RAM to the memory mapping. As MongoDB updates and reads from the DB it is reading and writing to RAM. All indexes on the documents in the database are held in RAM also. The files in RAM are flushed to disk every 60 seconds. To prevent data loss in the event of power failure, the default is to run with journaling switched on. The journal file is flushed to disk every 100ms and if there is power loss is used to bring the database back to a consistent state. An important design decision with mongo is on the amount of RAM. You need to figure out your working set size - i.e if you are going to be reading and writing to only the most recent 10% of your data in the database then this 10% is your working set and should be held in memory for maximum performance. So if your working set is 10GB you are going to neen 10GB for max performance - otherwise your queries/updates will run slower as pages of memory are paged from disk into memory. Other important aspects of mongoDB are replication for backups and sharding for scaling. There are a lot of great online resources for learning. MongoDB is free and opensource.</p> <p>EDIT: It's a good idea to check out the tutorial <a href="http://www.mongodb.org/display/DOCS/Tutorial" rel="noreferrer">http://www.mongodb.org/display/DOCS/Tutorial</a> and manual <a href="http://www.mongodb.org/display/DOCS/Manual" rel="noreferrer">http://www.mongodb.org/display/DOCS/Manual</a> and the Admin Zone is useful too <a href="http://www.mongodb.org/display/DOCS/Admin+Zone" rel="noreferrer">http://www.mongodb.org/display/DOCS/Admin+Zone</a> and if you get bored of reading then the presentations are worth checking out. <a href="http://www.10gen.com/presentations" rel="noreferrer">http://www.10gen.com/presentations</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload