Project

Profile

Help

Refactor #8821

Task #8488: [EPIC] Upgrade to django 3.2

Have the content app make all of its ORM calls in another Threadpool executor

Added by bmbouter 5 months ago. Updated 4 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
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.

Associated revisions

Revision 91a57d3e View on GitHub
Added by dalley 5 months ago

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

History

#1 Updated by dalley 5 months ago

  • Status changed from NEW to POST
  • Assignee set to dalley

#2 Updated by dalley 5 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#3 Updated by pulpbot 4 months ago

  • Sprint/Milestone set to 3.14.0

#4 Updated by pulpbot 4 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF