Skip to content

Bump CI memory limits for performance and demo (full) targets#45

Merged
tomusdrw merged 3 commits into
mainfrom
td-bump-spacejam-mem-2048
May 8, 2026
Merged

Bump CI memory limits for performance and demo (full) targets#45
tomusdrw merged 3 commits into
mainfrom
td-bump-spacejam-mem-2048

Conversation

@tomusdrw
Copy link
Copy Markdown
Member

@tomusdrw tomusdrw commented May 8, 2026

Summary

  • Bump performance memory limit to 2048m for spacejam and jambda (mirrors the earlier jamduna bump in Bump jamduna performance memory to 2048m #43).
  • Bump demo (full) memory limit to 8192m for all 23 targets — adds docker_memory: '8192m' where it was unset (default 2048m) and raises explicit values that were below 8192m. javajam was already at 8192m and is unchanged.

Test plan

  • Manually trigger one of the demo (full) workflows via workflow_dispatch and confirm the target runs with the new memory limit.
  • Manually trigger spacejam / jambda performance workflows and confirm the bumped limit takes effect.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Increased container memory allocations for demo and performance workflows to improve stability and reliability (most demo runs now use 8192m; some performance jobs use 2048m).

tomusdrw and others added 2 commits May 7, 2026 23:28
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 8, 2026

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f9654aff-dde7-4d77-b86c-f018ead95f17

📥 Commits

Reviewing files that changed from the base of the PR and between 22f32ab and 81abb2f.

📒 Files selected for processing (1)
  • .github/workflows/jam4s-demo-full.yml

📝 Walkthrough

Walkthrough

This PR uniformly increases Docker memory allocations across GitHub Actions workflows. Most demo workflows now allocate 8192m (8GB) to the reusable demo-source.yml workflow, while performance workflows allocate 2048m (2GB) to reusable-picofuzz.yml. This configuration change affects 25 workflow files spanning different targets.

Changes

Docker Memory Allocation Updates

Layer / File(s) Summary
Demo Workflows: New Memory Configuration (8GB)
.github/workflows/boka-demo-full.yml, .github/workflows/graymatter-demo-full.yml, .github/workflows/jambda-demo-full.yml, .github/workflows/jamduna-demo-full.yml, .github/workflows/jamixir-demo-full.yml, .github/workflows/jampy-demo-full.yml, .github/workflows/jampy-recompiler-demo-full.yml, .github/workflows/jamzig-demo-full.yml, .github/workflows/jamzilla-demo-full.yml, .github/workflows/jamzilla-int-demo-full.yml, .github/workflows/new-jamneration-demo-full.yml, .github/workflows/pyjamaz-demo-full.yml, .github/workflows/spacejam-demo-full.yml, .github/workflows/tessera-demo-full.yml, .github/workflows/tsjam-demo-full.yml, .github/workflows/turbojam-demo-full.yml, .github/workflows/typeberry-demo-full.yml, .github/workflows/vinwolf-demo-full.yml
Adds docker_memory: '8192m' to the demo job's with inputs passed to the demo-source.yml reusable workflow across 19 targets.
Demo Workflows: Memory Upgrade to 8GB
.github/workflows/jam4s-demo-full.yml, .github/workflows/jamforge-demo-full.yml, .github/workflows/jotl-demo-full.yml, .github/workflows/pbnjam-demo-full.yml
Upgrades existing docker_memory values from 4096m or 2048m to 8192m for 4 targets.
Performance Workflows: Memory Configuration (2GB)
.github/workflows/jambda-performance.yml, .github/workflows/spacejam-performance.yml
Adds docker_memory: '2048m' to the test job's with inputs passed to the reusable-picofuzz.yml reusable workflow across 2 performance targets.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • FluffyLabs/jam-testing#39: Modifies reusable workflow invocations in multiple demo and performance workflow files with docker_memory parameter changes.
  • FluffyLabs/jam-testing#45: Both PRs modify the same GitHub Actions workflow inputs (adding/updating jobs.demo.with.docker_memory).
  • FluffyLabs/jam-testing#14: Previously adjusted pbnjam workflow memory allocation related to this PR's subsequent changes.

Poem

🐰 I hopped through YAML lines today,
Poked in memory where containers play,
Eight gigs for demos, two for speed,
CI hums on, with ample feed,
Hooray — the jobs have room to sway!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately summarizes the main change: bumping Docker memory limits for CI workflows targeting both performance and demo full environments across multiple targets.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch td-bump-spacejam-mem-2048

Comment @coderabbitai help to get the list of available commands and usage tips.

@tomusdrw tomusdrw merged commit 438b76d into main May 8, 2026
27 of 29 checks passed
@tomusdrw tomusdrw deleted the td-bump-spacejam-mem-2048 branch May 8, 2026 19:33
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