Because of the way its journaling is implemented with sync interval, when you've configured durability with `writeConcern` `j` set to `true`, any write will have to wait for the next sync interval to commit. This wait will be in the range of 0 to the configured interval (~100 ms) and that makes the worst case quite bad.
You can work around it by configuring a lower sync interval and thus less average wait time, but I doubt you ever reach the level of databases that were designed to prefer durability by default, and which have heavily optimized that write path.
Consider latency as an example. There's average latency and nth percentile latency (and a similar metric of % of requests above certain latency). You can plot the latency as a CDF (Cumulative distribution function) to visualize it differently. The amount of time you run the benchmark affects things, as performance is typically better 5 seconds in compared to 5 hours in. Performance consistency within a closely bounded temporal interval matters a lot too, as too spiky performance can be detrimental.
Is the same workload being performed? Are the machines configured similarly, or is one a replica cluster while another one is a slower NAS? Are the indexes similar? What is the read workload during that time, as no reads vs high reads affect write latency rate.
And we're just talking about one metric for a database. There are other related metrics -- like iops, cpu taken, memory taken, disk taken, disk writes, disk amplification (io per op), etc, that all 'matter'.
You also seem to be assuming mongodb is the fastest database out there (is it still faster?). That's a fragile assumption.