Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Cloud Databases Programming Python

Testing the MongoDB Global Write Lock Improvements 38

Posted by Unknown Lamer
from the heckling-haskell-hackers dept.
rick446 writes "I took some time to benchmark the global write lock improvements in MongoDB 2.0. From the article: 'MongoDB, as some of you may know, has a process-wide write lock... Per-database and per-collection locking is on the roadmap ..., but it's not here yet. What was announced in MongoDB version 2.0 was locking-with-yield. I was curious about the performance impact of the write lock and the improvement of lock-with-yield, so I decided to do a little benchmark, MongoDB 1.8 versus MongoDB 2.0.'"
This discussion has been archived. No new comments can be posted.

Testing the MongoDB Global Write Lock Improvements

Comments Filter:

"You know, we've won awards for this crap." -- David Letterman

Working...