0.7 beta release of Motor, the async MongoDB Driver

[A. Jesse Jiryu Davis]

Hi friends, please try the beta release of Motor 0.7 and let me know how it works for you:

python -m pip install motor==0.7b0

Documentation:

• Motor beta documentation
• Motor 0.7 changelog

In two ways, Motor 0.7 paves the way for Motor 1.0: First, for asynchronous I/O, Motor now uses a thread pool. It no longer needs the "greenlet" package, and it now requires the "futures" backport package on Python 2.

See my blog post explaining the change.

Second, Motor 0.7 upgrades its PyMongo dependency from 2.8 to 2.9, and it wraps all the new PyMongo 2.9 APIs. This provides you a bridge from Motor's legacy API to the new APIs that will be required in Motor 1.0, and it supports all the latest MongoDB 3.2 features. See the Motor 1.0 Migration Guide.

Try the beta and let me know how it goes. Tell me about bugs, and also tell me if the beta works for you, so I can release Motor 0.7 confidently.

Peace,
—A. Jesse Jiryu Davis

[aliane abdelouahab]

so magic! i came here to ask for the release date of the new motor  that will implement the new mongodb api!

thank you :D

[Aliane Abdelouahab]

"Why isn't the event loop best for database communications? It's
because database operations should be quick. Since their durations are
short, the connection pool doesn't grow past a few dozen sockets."

So how about GridFS for example, will the threadpool be better?
And since Greenlet is no more used, that means this will speed up on PyPy?

> --
> You received this message because you are subscribed to the Google Groups
> "Tornado Web Server" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to python-tornad...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[A. Jesse Jiryu Davis]

The same logic applies to GridFS, and Motor 0.7 will use a thread pool for GridFS the same as it does for all MongoDB communication.

I haven't re-tested PyPy, that's a very interesting question. Right now, PyPy doesn't support native coroutines with "async" and "await", so I would say that CPython 3.5 still has a performance advantage, and it's still the best way to run Motor applications. But there may be particular Motor applications that run faster in PyPy.

> email to python-tornado+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Tornado Web Server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to python-tornado+unsubscribe@googlegroups.com.

[Aliane Abdelouahab]

I guess it will be amazing now, because I remember I saw benchmarks
about motor, and it was said that motor, because it uses greenlets,
dident give good resultst on pypy, but now that it will not use it,
this will be good (for those who will not use python 3.5 like
coroutines).
Thank you again ^_^

>> > email to python-tornad...@googlegroups.com.

>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Tornado Web Server" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to python-tornad...@googlegroups.com.

>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Tornado Web Server" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to python-tornad...@googlegroups.com.