MongoDB Configuration File Tuning
For those of us
who are regular to MySQL, its configuration file (my.cnf) and the many
options in it (some may say too many), mongoDB seems to be the simple.
With only few dozens of parameters in the configuration file (mongo.conf) and a dozen that are actually related to performance tuning, it may be a relatively short task to tune a mongoDB configuration file. Probably some of us will pay for that in production...
NOTE: this post does not refer the Sharding configuration.
What Can be Done?
Number of Connections
Like many other products (Apache httpd, MySQL...) the number of user connections can affect performance. mongoDB supports that using maxConns = N. Numbers can reach 20,000, but you should adjust it to your own server resources.
Write to Disk
Disk writing is usually a bottleneck in database systems. Therefore, wrtie to disk frequency and initial storage allocation can highly effect your system performance. Yet notice that delaying disk writing can effect your system recovery (many of you probably familiar with it from MySQL).
You should notice the following two options:
- Delay journal (database log) write to disk using journalCommitInterval = 300. This parameter supports intervals between 2ms (slowest but safest for recovery) and 300ms (fastest but prone to recovery options). The default os 100ms, but you may increase it to 300ms to save resources.
- Preallicate space at mongoDB startup by keeping noprealloc = false.
mongoDB provides many supporting services. Disabling some of them (if you do not use them), may help you save some CPU cycles:
- BSON validation using objcheck = false.
- HTTP Interface using nohttpinterface = true.
- Scripting Engine using noscripting = true.
- REST service using rest = false.
- Profiling service (inc. slow queries logging) using profile = 0.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)