Find answers from the community

Updated 3 months ago

And to add on to this the new native

And to add on to this, the new native async support seems much worse than running a sync call with use_async=True inside an executor, I'm currently implementing this in a discord bot and using the new async, it blocks for the entire duration of the query and doesn't allow for execution pauses if another bot command is run while a query is happening, whereas using an executor and use_async, it successfully pauses execution in an async style to allow for new things to run

7 comments

jjerryjliu0

Interesting - that's a bit unexpected, the new async should largely follow the same async exec logic as the old

jjerryjliu0

thanks for surfacing

KKaveen

yeah, it seems that the exec logic is one big chunk now and doesn't allow for it to yield control if something else comes up? Did priorities change?

jjerryjliu0

Hmm interesting

KKaveen

If you don't see any issues on your end with this async stuff, let me know and I can try to show the snippets of my code that recreate issues

jjerryjliu0

tbh i haven't fully benchmarked it. let me investigate a bit today!

KKaveen

Thanks!!!

Add a reply