Motor uses ThreadPoolExecutor, it drastically decreases a performance

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.

Start by reviewing how the ODM integrates Motor and where ThreadPoolExecutor is used. The issue does not name files, tests, or a concrete design, so first establish the intended genuinely asynchronous approach and how performance will be measured; done requires an agreed implementation that avoids the reported performance decrease.

Written by the indexing model from the issue text.