Issue #6104: pulp_file performance test takes too long for Travis - File Support - Pulp

Send by e-mail

Issue #6104

pulp_file performance test takes too long for Travis

Added by daviddavis over 1 year ago. Updated over 1 year ago.

Status:

NEW

Priority:

Normal

Assignee:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

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