Skip to content
Snippets Groups Projects

Resolve "Romeo SMT enabled by default?"

Merged Sebastian Döbel requested to merge 476-fix-remeo-smt into preview
1 unresolved thread

Closes #476 (closed)

To get 256 cores per node --hint=multithread has to be specified or SLURM returns salloc: error: Job submit/allocate failed: Requested node configuration is not available This shows SMT is diabled per default and has to be enabled by the user

Furthermore I added a note how to activate SMT on alpha partition similar to romeo

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Then we should change it in both cases. Any suggestion on how to say it is disabled per default?

  • Like this it should be fine: You mentioned it on the AMD Rome page as the first note - this is good.
    On this page it should not be too much detail. Hence 'available' fits well in my eyes. For me the terms mean
    "disabled": has been turned off by the admins, is not possible to get on the specified partitions.
    "enabled": is active and turned on (definition: "aktiviert", "betriebsbereit", "aktiv")
    "available": is configured and can be used, but requires action (definition: "erhältlich", "verfügbar", "vorhanden")

  • Sebastian Döbel added 17 commits

    added 17 commits

    Compare with previous version

  • Sebastian Döbel added 18 commits

    added 18 commits

    Compare with previous version

    • Es ist sowohl auf der Partition romeo* als auch alpha* SMT verfügbar, jedoch muss man bei den Parametern aufpassen. Da wir auf den Login-Knoten SLURM_HINT=nomultithread gesetzt haben, gibt es zwei Wege.

      1. Für sbatch:
        1. unset SLURM_HINT
        2. --slurm-hint=multithread im Batch-Skript nutzbar
      2. Für srun und salloc kann man den Parameter --slurm-hint=multithread benutzen
    • Beide Methoden sollten in den betreffenden Unterseiten bereits angegeben sein.

      Edited by Sebastian Döbel
    • Das Unerwartete ist hier, das im sbatch Skript--hint=multithread die Umgebungvariable nicht überschreibt. D.h., ob das Script überhaupt ausführbar ist, hängt von der Umgebung des Nutzers ab.

      Laut DOKU wird --hint höher nur höher eingestuft als SLURM_HINT, wenn es tatsächlich als command line argument mitgegeben wird: sbatch --hint=multithread <sbatch.script>. Die Angabe, dass man mit --hint=... im sbatch Skript SMT genutzt werden kann, ist daher falsch.

      --hint=<type>
          Bind tasks according to application hints.
          NOTE: This option cannot be used in conjunction with --ntasks-per-core, --threads-per-core
      or -B. If --hint is specified as a command line argument, it will take precedence over the
       environment.
      Edited by Maximilian Sander
    • Please register or sign in to reply
  • Man kann auch immer die Umgebungsvariable mit export SLURM_HINT=multithread überschreiben.

  • added 1 commit

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • Martin Schroschk requested review from @s8916149--tu-dresden.de and removed review request for @rotscher--tu-dresden.de

    requested review from @s8916149--tu-dresden.de and removed review request for @rotscher--tu-dresden.de

  • Sebastian Döbel approved this merge request

    approved this merge request

  • added 1 commit

    • 165b164c - Apply 1 suggestion(s) to 1 file(s)

    Compare with previous version

  • mentioned in commit ea67e57b

  • Please register or sign in to reply
    Loading