Actions
Refactor #8821
closed
Task #8488: [EPIC] Upgrade to django 3.2
Have the content app make all of its ORM calls in another Threadpool executor
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Django 3.2 will complain if we call into the ORM from inside a coroutine. So we should change the ORM calls to occur not from within a coroutine.
Actions
.
Pass blocking IO in content handler to a threadpool executor
The standard async executor is single-threaded and blocking IO shreds its throughput. Let's create a separate executor for blocking IO.
fixes: #8821 https://pulp.plan.io/issues/8821