Project

Profile

Help

Issue #6104

pulp_file performance test takes too long for Travis

Added by daviddavis 8 months ago. Updated 7 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

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

[1] https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#usage-limits


Related issues

Related to Pulp - Issue #6121: Syncs of very large repositories take longer than Pulp 2CLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by daviddavis 8 months ago

  • Description updated (diff)

#2 Updated by fao89 8 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 66

#3 Updated by daviddavis 8 months 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 8 months ago

  • Related to Issue #6121: Syncs of very large repositories take longer than Pulp 2 added

#5 Updated by rchan 7 months ago

  • Sprint changed from Sprint 66 to Sprint 67

#6 Updated by rchan 7 months ago

  • Sprint changed from Sprint 67 to Sprint 68

#7 Updated by rchan 7 months 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

Also available in: Atom PDF