MongoDB – count current read/write operations

It is not a great practice to mix the app and database on the same server. You're competing for resources. You also mentioned remote execution versus local execution on the same disk. I'd contend that you could suffer from disk contention if it was all on the same disk and the overhead of the remote replication is questionable by comparison. A lot of factors play into that including the type of disk(s) and if you are separating the OS, logs, and data.

Regarding your topology, yes a best practice in any DB technology is to place replica set members in a different datacenter. Pending your disaster recovery requirements, having at least one of those close to the primary node would be beneficial. There are other considerations such as an emergency on one coast of the US for example that makes all 3 unavailable. That is a case by case scenario to consider though. You also should consider your read and write concerns when addressing performance and availability. The default write concern will be 1. If your greater concern is availability; you may want to use a WC of 2 or majority in the example you gave. Testing your workload will only prove this for your use case and the WC can be set per operation so if you have some operations that are less important you could just use a less reliable WC. You should explore the bulk insert method as well. Personally for time-series data I have found the default and maximum batch of 1000 to be very good. I've also had good results increasing it to 5000 and allowing the DB engine break the batches out into 1k batches. Anything after that has demonstrated poorer inserts per second.

It is quite a lengthy topic but these are some ideas.

MMS charts have multiple quantities you can add to determine the number of reads and the number of writes - at a glance they are:

• Reads:

  • queries
  • getmores

• Writes:

  • inserts
  • updates
  • deletes/removes

As a general ballpark value, the ratio of these is fine.

It's not quite this simple though because there are other read and write "loads" on the system:

• system writes which don't show up in counters, such as TTL deletes, etc.
• commands which may be reads: count, aggregate, in 2.4 and earlier getLastError().
• commands which may be writes: findAndModify, etc.
• on a primary a multi-update or remove that matches multiple documents is recorded as a single write operation (on secondary it would be a single write per document affected)
• a single read operation (aka find) may be a fast, indexed query or a slow collection scan of millions of documents.

Hope this helps, as in general you usually care about not exact absolute ratio of reads to writes, but rather how that ratio may be changing over time.