CODEWITHSUNDEEP
mysqlrubyruby-on-rails-3mongodb
Daniel Blaichinger
Daniel Blaichinger

Reputation: 348

Rails 3: Measure database performance (MongoDB and MySQL)

I set up my Rails application twice. One is working with MongoDB (Mongoid as mapper) and the other with MySQL and ActiveRecord. Then I wrote a rake task which inserts some test-data to both databases (100.000 entries). I measured how long it takes for each database with the ruby Benchmark module. I did some testing with 100 and 10.000 entries where mongodb was always faster than mysql (about 1/3). The weird thing is that it takes about 3 times longer in mongodb to insert the 100.000 entries than with mysql. I have no idea why mongodb has this behaviour?! The only thing that I know is that the cpu time is much lower than the total time. Is it possible that mongodb starts some sort of garbage collection while it's inserting the data? At the beginning it's fast, but as more data mongodb is inserting, it gets slower and slower...any idea on this?

To get somehow a read performance of the two databases, I thought about measuring the time when the database gets an search query and respond the result. As I need some precise measurements, I don't want to include the time where Rails is processing my query from the controller to the database.

How do I do the measurement directly at the database and not in the Rails controller? Is there any gem / tool which would help me?

Thanks in advance!

EDIT: Updated my question according to my current situation

Upvotes: 0

Views: 1395

Answers (2)

Asya Kamsky
Asya Kamsky

Reputation: 42342

If your base goal is to measure database performance time at the DB level, I would recommend you get familiar with the benchRun method in MongoDB.

To do the type of thing you want to do, you can get started with the example on the linked page, here is a variant with explanations:

// skipped dropping the table and reinitializing as I'm assuming you have your test dataset
// your database is called test and collection is foo in this code
ops = [
// this sets up an array of operations benchRun will run
   { 
      // possible operations include find (added in 2.1), findOne, update, insert, delete, etc.
      op : "find" ,   
      // your db.collection
      ns : "test.foo" ,  
      // different operations have different query options - this matches based on _id
      // using a random value between 0 and 100 each time
      query : { _id : { "#RAND_INT" : [ 0 , 100 ] } }
   }
]

for ( x = 1; x<=128; x*=2){
    // actual call to benchRun, each time using different number of threads
    res = benchRun( { parallel : x ,   // number of threads to run in parallel
                      seconds : 5 ,    // duration of run; can be fractional seconds
                      ops : ops        // array of operations to run (see above)
                    } )
    // res is a json object returned, easiest way to see everything in it:
    printjson( res )
    print( "threads: " + x + "\t queries/sec: " + res.query )
}

If you put this in a file called testing.js you can run it from mongo shell like this:

> load("testing.js")
{
    "note" : "values per second",
    "errCount" : NumberLong(0),
    "trapped" : "error: not implemented",
    "queryLatencyAverageMs" : 69.3567923734754,
    "insert" : 0,
    "query" : 12839.4,
    "update" : 0,
    "delete" : 0,
    "getmore" : 0,
    "command" : 128.4
}
threads: 1   queries/sec: 12839.4

and so on.

Upvotes: 1

Daniel Blaichinger
Daniel Blaichinger

Reputation: 348

I found the reason why MongoDB is getting slower while inserting many documents.

Many to many relations are not recommended for over 10,000 documents when using MRI due to the garbage collector taking over 90% of the run time when calling #build or #create. This is due to the large array appending occuring in these operations. http://mongoid.org/performance.html

Now I would like to know how to measure the query performance of each database. My main concerns are the the measurement of the query time and the flow capacity / throughput. This measurement should be made directly at the database, so that nothing can adulterate the result.

Upvotes: 0

Related Questions