Skip to content

run-souffle: one engine compile per engine id - #1721

Merged
swapnilpaliwal-sd merged 1 commit into
0.1.7from
fix/souffle-compile-lock
Sep 28, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
0.1.7from
fix/souffle-compile-lock

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

Concurrent runs that missed the engine cache (a suite running cases concurrently since #1680, several agents on one machine) each compiled the same engine, a multi-GB c++ per run, enough at once to run a 128 GB machine out of memory. A lock per engine id now lets one run compile while the others wait and reuse its binary; a lock older than 30 min (a killed compile) is taken over.

Checked: the JS suite from a cold cache with 8 concurrent cases passes 75/75 and builds one engine binary.

… and reuse it

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit 4baef39 into 0.1.7 Sep 28, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the fix/souffle-compile-lock branch September 28, 2026 23:06
@swapnilpaliwal-sd swapnilpaliwal-sd mentioned this pull request Sep 29, 2026
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.

1 participant