Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
R runOPAL
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • runOPAL
  • Issues
  • #7

Closed
Open
Created Apr 19, 2018 by Valeria Rizzoglio@rizzoglio_v

Suggested improvements for Merlin5

Here the suggestions from a discussion with Dmitry Ozerov:

1- prepare a single slurm script containing an array of jobs

ex: sbatch -a 1-100 test.sh

this will submit in one command 100 jobs to slurm. The trick to be nice with the other users:

sbatch -a 1-100%10 test.sh

(or similar %25, %50)

2- nodes and tasks:

for ntasks < 16 than it would be more meaningful to ensure that the ntasks run on the same node. Now:

#SBATCH --ntasks=4

#SBATCH --ntasks-per-node=4

suggested:

#SBATCH --ntasks=4

#SBATCH --nodes=1

3- Loading modules in slurm script

module load gcc.....

so everything what is needed to load, setup to run the job (otherwise it's a dependence on what there is in .bashrc or environment (from which the job is submitted).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking