Tokumx vs Mongodb, tokumxvsmongodb

Tokumx vs Mongodb, tokumxvsmongodb

Mongodb is a document-type nosql database. The biggest advantage of using C ++ to write Mongo DB is that all data persistence operations do not require developers to manually write SQL statements, CRUD operations can be easily implemented by directly calling methods. Many people think that mongodb does not support transactions. In fact, mongodb is not a fully transactional database, and some of its operations are transaction processes. Here I want to recommend another database similar to mongo, tokumx, which is the open-source version of tokuek. It can be said that he has the same nosql features as mongo and the transaction features of relational databases, and supports document-level locks. Below we will briefly compare their advantages and disadvantages,

1. Insert Performance Comparison

Tokumx is several times better than mongodb in terms of reading and writing. I tested it on a single machine. The insertion time of 1 million pieces of data is about three times that of tokumx in mongodb.

2. IPOS comparison

IPOS refers to the number of read/write (I/O) operations per second. We know that the hard disk service life is limited. The more I/O operations, the shorter the service life, tokumx uses the TokuMX Fractal Tree (R) indexes), which is a batch version of B-Tree, which can effectively reduce IO times and improve read/write efficiency.

3. Comparison of Data Compression Efficiency

Tokumx supports three compression algorithms: "quicklz", "lzma", and "zlib", which saves more than 90% space storage space compared with mongo, therefore, tokumx can be used for large log storage.

4. Other features of tokumx

* Oplog supports daily partitioning. You can set an expiration time based on expireOplogDays to delete expired Oplog files to relieve disk pressure.
* Optimized multipart block migration, removing many global locks and database-level locks, simplifying and optimizing data transfer between different slices
* Document-level locks, non-Db-level, non-Collection-level locks!
* Supports ACID and MVCC features
* Do not worry about disk data fragmentation!
* Self-controlled memory instead of being handed over to the system for control, unlike mongodb's use of MMAP memory for control

* Better cluster capabilities than mongodb

PS: The last thing to note is, why is tokumx so much more powerful than mongodb, but not much used? The reason is that the probability of the tokumx process crash dropping is much higher than that of mongo --#

C # how to operate Mongodb in VS2010

I cannot tell you clearly. Let's show you a person's blog.
Www.cxybase.com/..8e424a2/

Help: update the MongoDB sub-document in C #. The format in my database is as follows:

Update set lou = '7' where name = test and age = 20