source-academy / backend / 16cc7e5f5048bfcb694c82b04709e0b31b1923bd-PR-1363

87%

master: 90%

Build Type

Pull #1363

github

Committed by RichDom2185

Commit Message

Give autograder result storage its own queue

`ResultStoreWorker` was `use Que.Worker, concurrency: 5` before the move
to Oban, deliberately separate from the grading work so that database
writes stayed bounded -- as its `@moduledoc` still says:

    Separate worker is created with lower concurrency on the assumption
    that autograding time >> db IO time so as to reduce db load.

Putting it on the same `autograder: 20` queue as `LambdaWorker` lost
both halves of that: result jobs now queue behind a batch's Lambda
invocations, and up to 20 of them can then write to the database at
once.

Restore the separation with a dedicated `autograder_results: 5` queue.

Reported in review: PR #1363.

Pull Request Pull Request #1363: Upgrade most dependencies and modernize codebase

Coverage Stats

81 of 103 new or added lines in 17 files covered. (78.64%)

26 existing lines in 7 files now uncovered.

4055 of 4630 relevant lines covered (87.58%)

6919.45 hits per line