I’ve been using Mongo 3.6 as an embedded message queue for a while now, and I’m circling back around investigating bumping up to the latest version (4.2). In order to use many of the new features, MongoDb must be running as a replica set (this is a stand-alone deployment).
When moving from a non-replica-set standalone, to a replica-set standalone, I’m seeing at 40% drop in insert performance and a 60% over drop in read/write performance!
Has anyone else experienced a similar hit when moving to a replica-set? Seems like way too much of an impact, and I’m wondering if I’ve missed something…
I should add that I’m seeing this on Win10.