Announcement

Collapse
No announcement yet.

MongoDB 3.0 To Have WiredTiger, Big Performance Improvements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MongoDB 3.0 To Have WiredTiger, Big Performance Improvements

    Phoronix: MongoDB 3.0 To Have WiredTiger, Big Performance Improvements

    MongoDB 3.0 was announced today with an expected GA release in March. MongoDB 3.0 has "massive improvements to performance and scalability, enabled by comprehensive improvements in the storage layer."..

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    "Default database" my a$$. As soon as you try to deploy a global cluster, the single master limitation will bite you hard. And if you don't need a global cluster, you don't need MongoDB (or any other NoSQL solution).

    Comment


    • #3
      Originally posted by bug77 View Post
      And if you don't need a global cluster, you don't need MongoDB (or any other NoSQL solution).
      Bullshit. A bunch of tables is far from the optimal storage solution for many kinds of applications. Buy storing data in a form closer to your domain you reduces code complexity and pitfalls of wrongly modeling of the data.

      Comment


      • #4
        Originally posted by Pajn View Post
        Bullshit. A bunch of tables is far from the optimal storage solution for many kinds of applications. Buy storing data in a form closer to your domain you reduces code complexity and pitfalls of wrongly modeling of the data.
        REAL databases like PostgreSQL are better than these NoSQL databases any day. The only thing that they don't do is sharding and horizontal scaling.

        And if you want to treat a SQL database as a key value store you can. PostgreSQL even has a data type specialized for it, the HSTORE.

        If you want great performance and no data integrity then you should be using Redis. As grandparent says, only if you need big storage and horizontal scaling should you use Mongo, Cassandra, etc.

        Comment


        • #5
          Originally posted by Zan Lynx View Post
          As grandparent says, only if you need big storage and horizontal scaling should you use Mongo, Cassandra, etc.
          Grandpa is wrong. Great reasons to use MongoDB:

          1) Free-form document structure is a huge boon to development iteration.
          2) MongoDB offers atomic operations, which many other NoSQL databases don't. Without this integrated into the database, you have to manage locking on your own (ZooKeeper, etc.).
          3) Good and very easy-to-use indexing features that are aware of the JSON structure of your documents.

          Notice how I didn't mention scalability at all. All databases can be made to scale well. Remember that Twitter runs on MySQL as its foundation (with FlockDB on top of it).

          Comment


          • #6
            Originally posted by emblemparade View Post
            Grandpa is wrong. Great reasons to use MongoDB:

            1) Free-form document structure is a huge boon to development iteration.
            2) MongoDB offers atomic operations, which many other NoSQL databases don't. Without this integrated into the database, you have to manage locking on your own (ZooKeeper, etc.).
            3) Good and very easy-to-use indexing features that are aware of the JSON structure of your documents.

            Notice how I didn't mention scalability at all. All databases can be made to scale well. Remember that Twitter runs on MySQL as its foundation (with FlockDB on top of it).
            I am a big PostgreSQL fan. All of that can be done in PostgreSQL 9.2+ with far more reliability. It used to be faster too, but I haven't run any tests against the new version of Mongo.

            Comment

            Working...
            X