My name is Bernardo Heynemann and I'm the creator and (currently) only committer on MotorEngine.
I did some benchmarks (although anecdotal) on Motor, PyMongo, MongoEngine and MotorEngine.
What I found out is that when performing database operations, pyMongo and MongoEngine are WAY faster than Motor and MotorEngine (which I kind of expected, due to the way tornado asyncs stuff enqueueing it in the ioloop).
That said, when using Tornado under some stress, they all yielded the same number of requests per second (roughly), which I concluded means not blocking actually pays off.
I haven't pursued this more because MotorEngine is still very much work in progress. Once it's more stable I'll try to get a much more comprehensive benchmark suite. I still believe that even if the requests are SLOWER (which they will be) it does pay off releasing the IoLoop to make sure you get to accept the next request.
Comment
Hi Peter,
My name is Bernardo Heynemann and I'm the creator and (currently) only committer on MotorEngine.
I did some benchmarks (although anecdotal) on Motor, PyMongo, MongoEngine and MotorEngine.
What I found out is that when performing database operations, pyMongo and MongoEngine are WAY faster than Motor and MotorEngine (which I kind of expected, due to the way tornado asyncs stuff enqueueing it in the ioloop).
That said, when using Tornado under some stress, they all yielded the same number of requests per second (roughly), which I concluded means not blocking actually pays off.
I haven't pursued this more because MotorEngine is still very much work in progress. Once it's more stable I'll try to get a much more comprehensive benchmark suite. I still believe that even if the requests are SLOWER (which they will be) it does pay off releasing the IoLoop to make sure you get to accept the next request.
What do you think?
Cheers,
Bernardo Heynemann