Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
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:
  • by Anonymous Coward on Monday January 02, 2012 @11:45PM (#38569340)

    It's like this articles starts in the middle of a sentence and I can't tell what the hell is going on.

    OK, for starters, what the fuck is MongoDB? Just a single sentence or some mention would be helpful. Secondly, why is this front page material? It's just some crappy blog about some minor change to some product nobody uses, woopdeedoo.

  • Pushing locks down (Score:3, Insightful)

    by Anonymous Coward on Tuesday January 03, 2012 @12:33AM (#38569556)

    Congratulations. You matter enough to bother reinventing this wheel again. If you continue to matter for a meaningful amount of time you'll end up locking individual documents, or whatever you call them. Oracle called that 'row' locking. 15 years ago.

  • by Anonymous Coward on Tuesday January 03, 2012 @12:57AM (#38569648)

    Yeah, we're nerds here. We like boring shit, fuck off.

You're already carrying the sphere!

Working...