Try to optimize test pipelines with lower CPU request

Created on 23 August 2024, 6 months ago

Problem/Motivation

This is mostly a test-bed for #3469828: Lower default concurrency because Paragraphs has one of the bigger contrib test suites that I know of. But there might be something to actually change here if it works.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @catch
  • Merge request !140Add a comment. → (Open) created by catch
  • Pipeline finished with Success
    6 months ago
    Total: 561s
    #262198
  • Pipeline finished with Success
    6 months ago
    Total: 323s
    #262208
  • Pipeline finished with Success
    6 months ago
    Total: 832s
    #262215
  • Pipeline finished with Success
    6 months ago
    Total: 458s
    #262218
  • Pipeline finished with Success
    6 months ago
    Total: 486s
    #262233
  • Pipeline finished with Success
    6 months ago
    Total: 480s
    #262237
  • Status changed to Closed: works as designed 6 months ago
  • 🇬🇧United Kingdom catch

    OK well this doesn't work particularly well at all, would need a large percentage of kernel and unit tests to functional and functional js tests to be able to handle the lower concurrency, and because the CPU request expands upwards when there are spare CPUs on the machine, can't really tell at what point it gets CPU constrained with the current concurrency.

Production build 0.71.5 2024