mongo 3.2 and wiredtiger

Deadline
1

Have you tested deadline8 with mongo 3.2, and / or wiredtiger?
We have just upgraded to 3.0, and were wondering whether there is any benefit going to either 3.2 and/or wiredtiger.

Found this forum online:
groups.google.com/forum/#!msg/m … bx81-pLP4J

Which suggested it was not a clear cut improvement.

2

Wiredtiger is definitely supposed to boost write-intensive workloads, but we haven’t done much performance testing since.

To be honest, the performance of the old storage engine has been pretty phenomenal, and we’ve been pretty conservative with technology and code changes. Vibhu tells me there is better lock performance on a per-db perspective since the locking happens at the document level.

If you’re willing to throw science at the wall, it might stick.
youtube.com/watch?v=UM-wKQqBBnY

3

I share the sentiment, so we will defer upgrading to that storage engine till you guys have tested it and recommend a switch.

thanks!
laszlo