2 Code formatting is just for code
source | link

As per your system details the readahead is set to 16K16K. But as per MongoDB BOL HereMongoDB BOL for the WiredTiger storage engine. Set the readahead setting to 00 regardless of storage media type (spinning, SSD, etc.).

Setting a higher readahead benefits sequential I/O operationssequential I/O operations. However, since MongoDBMongoDB disk access patterns are generally randomrandom, setting a higher readahead provides limited benefitlimited benefit or performance degradationperformance degradation. As such, for most workloads, a readahead of 00 provides optimal MongoDB performance. In general, set the readaheadreadahead setting to 0 unless testing shows a measurable, repeatable, and reliable benefit in a higher readaheadreadahead value. MongoDB Professional Support can provide advice and guidance on non-zero readahead configurations.

As MongoDB documentation for the WiredTiger, consider the following recommendations on Linux environment:

  1. Turn off atime for the storage volume containing the database files.
  2. Set the file descriptor limit, -n-n, and the user process limit (ulimitulimit), -u-u, above 20,000, according to the suggestions in the ulimitulimit reference. A low ulimitulimit will affect MongoDB when under heavy use and can produce errors and lead to failed connections to MongoDB processes and loss of service.
  3. Disable Transparent Huge Pages. MongoDB performs better with normal (4096 bytes) virtual memory pages. see Transparent Huge Pages Settings.
  4. Disable NUMANUMA in your BIOSBIOS. If that is not possible, see MongoDB on NUMA Hardware.

As per your system details the readahead is set to 16K. But as per MongoDB BOL Here for the WiredTiger storage engine. Set the readahead setting to 0 regardless of storage media type (spinning, SSD, etc.).

Setting a higher readahead benefits sequential I/O operations. However, since MongoDB disk access patterns are generally random, setting a higher readahead provides limited benefit or performance degradation. As such, for most workloads, a readahead of 0 provides optimal MongoDB performance. In general, set the readahead setting to 0 unless testing shows a measurable, repeatable, and reliable benefit in a higher readahead value. MongoDB Professional Support can provide advice and guidance on non-zero readahead configurations.

As MongoDB documentation for the WiredTiger, consider the following recommendations on Linux environment:

  1. Turn off atime for the storage volume containing the database files.
  2. Set the file descriptor limit, -n, and the user process limit (ulimit), -u, above 20,000, according to the suggestions in the ulimit reference. A low ulimit will affect MongoDB when under heavy use and can produce errors and lead to failed connections to MongoDB processes and loss of service.
  3. Disable Transparent Huge Pages. MongoDB performs better with normal (4096 bytes) virtual memory pages. see Transparent Huge Pages Settings.
  4. Disable NUMA in your BIOS. If that is not possible, see MongoDB on NUMA Hardware.

As per your system details the readahead is set to 16K. But as per MongoDB BOL for the WiredTiger storage engine. Set the readahead setting to 0 regardless of storage media type (spinning, SSD, etc.).

Setting a higher readahead benefits sequential I/O operations. However, since MongoDB disk access patterns are generally random, setting a higher readahead provides limited benefit or performance degradation. As such, for most workloads, a readahead of 0 provides optimal MongoDB performance. In general, set the readahead setting to 0 unless testing shows a measurable, repeatable, and reliable benefit in a higher readahead value. MongoDB Professional Support can provide advice and guidance on non-zero readahead configurations.

As MongoDB documentation for the WiredTiger, consider the following recommendations on Linux environment:

  1. Turn off atime for the storage volume containing the database files.
  2. Set the file descriptor limit, -n, and the user process limit (ulimit), -u, above 20,000, according to the suggestions in the ulimit reference. A low ulimit will affect MongoDB when under heavy use and can produce errors and lead to failed connections to MongoDB processes and loss of service.
  3. Disable Transparent Huge Pages. MongoDB performs better with normal (4096 bytes) virtual memory pages. see Transparent Huge Pages Settings.
  4. Disable NUMA in your BIOS. If that is not possible, see MongoDB on NUMA Hardware.
1
source | link

As per your system details the readahead is set to 16K. But as per MongoDB BOL Here for the WiredTiger storage engine. Set the readahead setting to 0 regardless of storage media type (spinning, SSD, etc.).

Setting a higher readahead benefits sequential I/O operations. However, since MongoDB disk access patterns are generally random, setting a higher readahead provides limited benefit or performance degradation. As such, for most workloads, a readahead of 0 provides optimal MongoDB performance. In general, set the readahead setting to 0 unless testing shows a measurable, repeatable, and reliable benefit in a higher readahead value. MongoDB Professional Support can provide advice and guidance on non-zero readahead configurations.

As MongoDB documentation for the WiredTiger, consider the following recommendations on Linux environment:

  1. Turn off atime for the storage volume containing the database files.
  2. Set the file descriptor limit, -n, and the user process limit (ulimit), -u, above 20,000, according to the suggestions in the ulimit reference. A low ulimit will affect MongoDB when under heavy use and can produce errors and lead to failed connections to MongoDB processes and loss of service.
  3. Disable Transparent Huge Pages. MongoDB performs better with normal (4096 bytes) virtual memory pages. see Transparent Huge Pages Settings.
  4. Disable NUMA in your BIOS. If that is not possible, see MongoDB on NUMA Hardware.