Issue #6104
pulp_file performance test takes too long for Travis
Description
Currently the pulp_file cron jobs are failing due to the performance tests. It looks like they are exceeding 50 minutes which is the threshold in Travis[0].
On my local box, it took about 24 seconds for pulp to process 400 content units. So for 100,000 units it would take about 100 minutes (100,000 / 400 * 24 / 60).
If we lowered the number of units to 10,000-20,000, the performance tests should complete under 50 minutes.
Alternatively, the maximum execution time in Github Actions is 6 hours[1].
[0] https://docs.travis-ci.com/user/customizing-the-build/#build-timeouts
Related issues
History
#1
Updated by daviddavis about 1 year ago
- Description updated (diff)
#2
Updated by fao89 about 1 year ago
- Triaged changed from No to Yes
- Sprint set to Sprint 66
#3
Updated by daviddavis about 1 year ago
Temporary PR to shrink the file-perf fixture and get Travis passing again: https://github.com/pulp/pulp-fixtures/pull/144
#4
Updated by daviddavis about 1 year ago
- Related to Issue #6121: Syncs of very large repositories take longer than Pulp 2 added
#5
Updated by rchan about 1 year ago
- Sprint changed from Sprint 66 to Sprint 67
#6
Updated by rchan about 1 year ago
- Sprint changed from Sprint 67 to Sprint 68
#7
Updated by rchan about 1 year ago
- Sprint deleted (
Sprint 68) - Tags CI/CD added
Remove from sprint. We have made some other adjustments Ci that lowers urgency of this work.
Please register to edit this issue