async/sync: offloading entire function call trees to starlette-managed threads (fully sync) VS thin sync-to-async wrappers (fully async)

[why-not-try-calmer]

async/sync: offloading entire function call trees to starlette-managed threads (fully sync) VS thin sync-to-async wrappers (fully async)

[why-not-try-calmer]

Just got the confirmation from a fastapi developer moderator: instead of wrapping each call with loop.run_in_executor(None, ...), define your route as def and Starlette (FastAPI) will wrap that whole function with loop.run_in_executor(None, ...).

[why-not-try-calmer]

Will update after profiling.

[why-not-try-calmer]

This issue is now solved with the recent commits to dev and to the MessageBroker. There is now instead an Issue to raise about threading, race conditions and the performance costs of Locks. But that's for another time...