Project

Profile

Help

Actions
Send by e-mail Copy link

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

Added by bmbouter almost 3 years ago. Updated almost 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
dalley
Category:
-
Sprint/Milestone:
3.14.0
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
Copy link
 #1

Updated by dalley almost 3 years ago

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

Added by dalley almost 3 years ago

Revision 91a57d3e | View on GitHub

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

Actions
Copy link
 #2

Updated by dalley almost 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by pulpbot almost 3 years ago

  • Sprint/Milestone set to 3.14.0
Actions
Copy link
 #4

Updated by pulpbot almost 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF