Skip to content

Remove halving of --max-memory value#717

Merged
yousefmoazzam merged 1 commit into
mainfrom
max-memory-halving
May 11, 2026
Merged

Remove halving of --max-memory value#717
yousefmoazzam merged 1 commit into
mainfrom
max-memory-halving

Conversation

@yousefmoazzam
Copy link
Copy Markdown
Collaborator

@yousefmoazzam yousefmoazzam commented May 11, 2026

Fixes IMGDA-841

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have made corresponding changes to the documentation
  • I have added the user-release-note label in order to include this PR in the "Notable
    Changes for Users" section in release notes

This is a leftover from when there was only GPU memory estimation (the
max slices estimation for GPU methods) in the framework and no CPU
memory estimation (the dataset store backing calculation, choosing
between RAM or an hdf5 file).

The max slices estimators of GPU methods all take into account the
output as well as the input needing to be stored in GPU memory, so
there's no need to halve the `--max-memory` value in order to account
for the size of the input and output of a section - the GPU method
memory estimators already account for this.

The CPU memory estimation in the dataset store backing calculator
accounts for the output chunk that will be written by a section in
addition to the input chunk being read by a section, so in the CPU
memory case there's also no need to do the halving of the `--max-memory`
value.
@yousefmoazzam yousefmoazzam merged commit 1b5b768 into main May 11, 2026
5 of 6 checks passed
@yousefmoazzam yousefmoazzam deleted the max-memory-halving branch May 11, 2026 11:20
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