Motor uses ThreadPoolExecutor, it drastically decreases a performance

[nikita-davydov]

Is there any plan to make this library really async?

It seems like that nobody who uses async motor understand that it's not really async.

[z0z0r4]

More information? This package uses motor by threading?

[nikita-davydov]

Just look into the sources of the official motor library: https://github.com/mongodb/motor/blob/master/motor/metaprogramming.py#L25

Any project that will use that for their requests to the mongoDB will have the performance decreased for sure.

[z0z0r4]

Just look into the sources of the official motor library: https://github.com/mongodb/motor/blob/master/motor/metaprogramming.py#L25

Any project that will use that for their requests to the mongoDB will have the performance decreased for sure.

Emmm, I have not enough ability to confirm is it true...

The cost is too much to achieve and maintain an unofficial async package as same as pymongo...

Any response in motor jira about this problem?

[nikita-davydov]

They just have the dead JIRA ticket about that so seems like they're not going to implement the real asyncio connection