Description of problem:
During very large (2.1TB) content import, pulp worker threads have spent almost 12 days reading the tar.gz export file.

This BZ is raised in relation to support case #03609607.


Version-Release number of selected component (if applicable):
6.11.5.4

How reproducible:
everytime

Steps to Reproduce:
1. place 2.1TB tar.gz file in to /var/lib/pulp/imports
2. run command: time hammer content-import version --organization-id=1 --path/var/lib/pulp/imports/z1d-export/


Actual results:
Import process ran for just shy of 12 days and resulted in failure.

Expected results:
Import process to take a substantially shorter amount of time.

Additional info:
Please see the support case #03609607 which has a lot more contextual information.
High IOWait is observed during the import process which lasts for over 11 days. The systems this has been tested on can sustain 1000MB/s disk throughput. The main testing system also has 24cpu and 192GB of memory.
Multiple tests of importing a 2.1TB content export that contains:
Repositories: 151 (both Red Hat and 3rd party repos)
RPM Packages: >200,000
Size of export: 2.1TB
During this import, the Dynflow Console showed the following line `2931: Actions::Pulp3::ContentViewVersion::CreateImport (skipped) [ 1003399.78s / 6400.08s ]`. This equals 11 days, 14 hours, 43 minutes out of the total import run time of 11 days, 14 hours, 59 minutes, 23 seconds. Whist the import was sitting at this task, there was still IOWait and looking the the pulpworkers, they were all reading the tar.gz of the export.

The import failed with a message of "7 subtask(s) failed for task group /pulp/api/v3/task-groups/.....". I will raise a separate BZ for the failure itself. This BZ is for the import speed.