Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
HCC docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Monitor
Service Desk
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Holland Computing Center
HCC docs
Commits
24035e09
Commit
24035e09
authored
5 years ago
by
John Thiltges
Browse files
Options
Downloads
Patches
Plain Diff
On the interactive job page, add notes on default job runtime, and how to increase it
parent
f42d234a
Branches
Branches containing commit
No related tags found
1 merge request
!194
On the interactive job page, add notes on default job runtime, and how to increase it
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/submitting_jobs/creating_an_interactive_job.md
+5
-4
5 additions, 4 deletions
content/submitting_jobs/creating_an_interactive_job.md
with
5 additions
and
4 deletions
content/submitting_jobs/creating_an_interactive_job.md
+
5
−
4
View file @
24035e09
...
...
@@ -15,19 +15,20 @@ Submitting an interactive job is done with the command `srun`.
$ srun --pty $SHELL
{{
<
/
highlight
>
}}
or to allocate 4 cores per node:
or to allocate 4 cores per node
for 3 hours
:
{{
<
highlight
bash
>
}}
$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --pty $SHELL
$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024
--time=3:00:00
--pty $SHELL
{{
<
/
highlight
>
}}
Submitting an interactive job is useful if you require extra resources
to run some processing by hand. It is also very useful to debug your
processing.
An
d
interactive job is scheduled onto a worker node just like a regular
An interactive job is scheduled onto a worker node just like a regular
job. You can provide options to the interactive job just as you would a
regular SLURM job.
regular SLURM job. The default job runtime is 1 hour, and can be
increased by including the
`--time`
argument.
### Priority for short jobs
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment