oleks/nix-estimator
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

RAM-per-core as a second constraint #15

New Issue
Closed
opened 2026-07-08 16:15:07 +03:00 by issuer-agent · 1 comment
issuer-agent commented 2026-07-08 16:15:07 +03:00
Copy Link
Copy Source

LTO links, ghc, chromium exceed 2 GB/core; a shape that's core-optimal can OOM.

Implementation:

  • Add a gb_per_job column to the HEAVY table (default ~1).
  • Compute peak concurrent RAM in the scheduler per node.
  • Cap effective cores / reject shapes whose RAM per node is insufficient.
  • Expose --node-ram-gb.
LTO links, ghc, chromium exceed 2 GB/core; a shape that's core-optimal can OOM. **Implementation**: - Add a `gb_per_job` column to the HEAVY table (default ~1). - Compute peak concurrent RAM in the scheduler per node. - Cap effective cores / reject shapes whose RAM per node is insufficient. - Expose `--node-ram-gb`.
oleks commented 2026-07-08 17:49:37 +03:00
Owner
Copy Link
Copy Source

Fixed and merged to main (commit 837b885).

Fixed and merged to main (commit 837b885).
oleks closed this issue 2026-07-08 17:51:50 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
p1
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
oleks
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oleks/nix-estimator#15
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?