Skip to content

Fix memory limits#566

Open
mxsrc wants to merge 2 commits intomainfrom
fix-memory-limits
Open

Fix memory limits#566
mxsrc wants to merge 2 commits intomainfrom
fix-memory-limits

Conversation

@mxsrc
Copy link
Collaborator

@mxsrc mxsrc commented Feb 2, 2026

The memory limits that are specified for the autoscaler have a few issues:

  • minimum is 2GiB, instead of our desired 512MiB
  • maximum is 32GiB which does not correspond to what the UI indicates
  • step size is 512MiB instead of 128

This PR

  • aligns the minima and maxima with the autoscaler configuration
  • drops the minimum to 512MiB
  • changes both steps to 256MiB
  • drops the maximum to 32GiB to align with the prior autoscaler definition

@mxsrc mxsrc force-pushed the fix-memory-limits branch from dff780d to 0df2eba Compare February 2, 2026 14:13
MEMORY_MAX = 32 * GIB
MEMORY_STEP = 256 * MIB
AUTOSCALER_MEMORY_SLOT_SIZE_MIB = MEMORY_STEP // MIB
AUTOSCALER_MEMORY_SLOTS_MIN = MEMORY_MIN // AUTOSCALER_MEMORY_SLOT_SIZE_MIB
Copy link
Collaborator

Choose a reason for hiding this comment

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

Wasn't there something like "the first chunk of memory must not be a virtio memory slot" and that's why we needed to split a chunk of normal memory and then memory slots?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Technically yes, but the autoscaler handles this transparently. The memory until the minimum is regular VM memory, anything beyond that is the pluggable memory but it's still talked about in terms of slots.

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