Project

General

Profile

Actions
Copy link

Bug #13570

closed

[Documentation] add how much extra overhead is added for RAM requirement when spinning up a compute node

Added by Bryan Cosca over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Peter Amstutz
Category:
-
Target version:
2018-08-01 Sprint
Story points:
-
Release:
Arvados 1.2
Release relationship:
Auto

Description

for example, if a user says ramMin 10000, what exactly does a-n-m spin a node up for?

docs might go in here: https://doc.arvados.org/user/cwl/cwl-style.html

Subtasks 1 (0 open — 1 closed)

Task #13589: Review 13570-crunch-ram-docResolvedTom Morris07/24/2018Actions
Actions
Copy link
 #2

Updated by Bryan Cosca over 6 years ago

What happens is c-d-slurm expects nodes to have 95% of the advertised memory size actually usable.

So the number that is specified in ramMin is multiplied by 100/95, which is the actual RAM requirement used to call a compute node.

Actions
Copy link
 #3

Updated by Tom Morris over 6 years ago

  • Target version set to 2018-06-20 Sprint
Actions
Copy link
 #4

Updated by Tom Morris over 6 years ago

  • Subject changed from [Documentation] add how much extra overhead is added when spinning up a compute node to [Documentation] add how much extra overhead is added for RAM requirement when spinning up a compute node
  • Assigned To set to Tom Morris
Actions
Copy link
 #5

Updated by Tom Morris over 6 years ago

  • Target version changed from 2018-06-20 Sprint to 2018-07-03 Sprint
Actions
Copy link
 #6

Updated by Tom Morris over 6 years ago

  • Target version changed from 2018-07-03 Sprint to 2018-07-18 Sprint
Actions
Copy link
 #7

Updated by Tom Morris over 6 years ago

  • Target version changed from 2018-07-18 Sprint to 2018-08-01 Sprint
Actions
Copy link
 #8

Updated by Peter Amstutz over 6 years ago

  • Assigned To changed from Tom Morris to Peter Amstutz
Actions
Copy link
 #9

Updated by Peter Amstutz over 6 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #11

Updated by Tom Morris over 6 years ago

doc/api/execution

  • Always capitalize Keep (I'm unsure about "container." Is the convention to capitalize it or not?)
  • Isn't cgroups used in the cloud as well? May not be intended, but sentence ordering kind of makes it sound like cgroups is HPC only

doc/user/cwl/cwl-style

  • "Available compute nodes" => "Available instance types" or "Available compute node types"
Actions
Copy link
 #12

Updated by Peter Amstutz over 6 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #13

Updated by Tom Morris about 6 years ago

  • Release set to 13
Actions
Copy link

Also available in: Atom PDF