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.