Issue #6104
closed
pulp_file performance test takes too long for Travis
Description
Ticket moved to GitHub: "pulp/pulp_file/623":https://github.com/pulp/pulp_file/issues/623
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
Updated by fao89 almost 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 66
Updated by daviddavis almost 5 years ago
Temporary PR to shrink the file-perf fixture and get Travis passing again: https://github.com/pulp/pulp-fixtures/pull/144
Updated by daviddavis almost 5 years ago
- Related to Issue #6121: Syncs of very large repositories take longer than Pulp 2 added
Updated by rchan almost 5 years 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.
Updated by pulpbot about 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
.