chore: Compare image memory limit to sum of shmem and main mem

[fregataa]

resolves #1726

This makes the behavior of the backend's interpretation of "mem" ($M$) and "shmem" ($S$) values consistent with the Web UI, which passes them as $(M-S, S)$ instead of $(M, S)$.

• Compare ai.backend.resource.min.mem with the sum of main memory size and shared memory size instead of main memory size.
• Configurable ratio between shared memory and memory.

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• Mention to the original issue
• API server-client counterparts (e.g., manager API -> client SDK)

[achimnol]

I'm going to hold this PR because the calculation method change will break existing API users (now we have serious ones) and complicates which values to store in the scheduler.

EDIT:
We decided to compare the image_min_slots["mem"] and requested_slots["mem"] directly (without adding shmem value to the former one), but add a check to prevent making shmem too large.

[fregataa]

• chore: Compare image memory limit to sum of shmem and main mem #1770 👈
• fix: Handle value error when convert shmem to binary size #2972
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @fregataa and the rest of your teammates on Graphite

[graphite-app]

The error message string is missing a closing parenthesis. The line should be:

f"(s:{str(shmem)}, m:{str(BinarySize(requested_slots['mem']))})"

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.