[DOCS-1624] Comment on: "manual/faq/developers.txt" Created: 19/Jun/13  Updated: 03/Nov/17  Resolved: 19/Jun/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: auto Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/faq/developers/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/536.30.1 (KHTML, like Gecko) Version/6.0.5 Safari/536.30.1
Referrer: http://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CDsQFjAB&url=http%3A%2F%2Fdocs.mongodb.org%2Fmanual%2Ffaq%2Fdevelopers&ei=i7_BUdCtEKLV0QXHjoGICw&usg=AFQjCNFWVKAVV0NRujfLV0TrvwCygbwm6A&sig2=jxCOhLU0zT1W1WbJunmMSA&bvm=bv.47883778,d.d2k
Screen Resolution: 2560 x 1440
repo: docs
source: faq/developers


Participants:
Days since reply: 10 years, 35 weeks ago

 Description   

Hey folks, suspect minor typo at the end of para #2 of the following section [... so that the above values resents a theoretical maximum].

Sorry, can't fix - Git n00b.

When does MongoDB write updates to disk?

MongoDB flushes writes to disk on a regular interval. In the default configuration, MongoDB writes data to the main data files on disk every 60 seconds and commits the journal roughly every 100 milliseconds. These values are configurable with the journalCommitInterval and syncdelay.

These values represent the maximum amount of time between the completion of a write operation and the point when the write is durable in the journal, if enabled, and when MongoDB flushes data to the disk. In many cases MongoDB and the operating system flush data to disk more frequently, so that the above values resents a theoretical maximum.

However, by default, MongoDB uses a “lazy” strategy to write to disk. This is advantageous in situations where the database receives a thousand increments to an object within one second, MongoDB only needs to flush this data to disk once. In addition to the aforementioned configuration options, you can also use fsync and getLastError to modify this strategy.


Generated at Thu Feb 08 07:41:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.