Skip to content

Restrict trigger-archivematica-lambda concurrency to 1 - #840

Merged
liam-lloyd merged 1 commit into
mainfrom
per-10750_restrict_trigger_archivematica_concurrency
Aug 13, 2026
Merged

Restrict trigger-archivematica-lambda concurrency to 1#840
liam-lloyd merged 1 commit into
mainfrom
per-10750_restrict_trigger_archivematica_concurrency

Conversation

@liam-lloyd

Copy link
Copy Markdown
Member

Archivematica is slow to process files, and it is more convenient for us if processing jobs build up in our SQS queues than Archivematica's internal queues. Thus there is no reason to scale up the trigger-archivematica-lambdas to feed files into Archivematica faster. In light of that, this commit restricts the concurrency of the trigger-archivematica-lambda to 1.

@codecov

codecov Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.67%. Comparing base (ce90814) to head (6b0757b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #840   +/-   ##
=======================================
  Coverage   98.67%   98.67%           
=======================================
  Files          98       98           
  Lines        2790     2790           
  Branches      530      531    +1     
=======================================
  Hits         2753     2753           
  Misses         37       37           
Flag Coverage Δ
api 98.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cecilia-donnelly cecilia-donnelly left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @liam-lloyd !

Archivematica is slow to process files, and it is more convenient for us
if processing jobs build up in our SQS queues than Archivematica's
internal queues. Thus there is no reason to scale up the
trigger-archivematica-lambdas to feed files into Archivematica faster.
In light of that, this commit restricts the concurrency of the
trigger-archivematica-lambda to 1.
@liam-lloyd
liam-lloyd force-pushed the per-10750_restrict_trigger_archivematica_concurrency branch from 4291f4f to 6b0757b Compare August 13, 2026 21:47
@liam-lloyd
liam-lloyd merged commit 80f84fb into main Aug 13, 2026
38 checks passed
@liam-lloyd
liam-lloyd deleted the per-10750_restrict_trigger_archivematica_concurrency branch August 13, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants