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
Merge requests
!160
Add section on GPU guest jobs.
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Add section on GPU guest jobs.
gpu_guest
into
master
Overview
0
Commits
1
Pipelines
0
Changes
1
Merged
Adam Caprez
requested to merge
gpu_guest
into
master
5 years ago
Overview
0
Commits
1
Pipelines
0
Changes
1
Expand
0
0
Merge request reports
Compare
master
master (base)
and
latest version
latest version
5457d7ae
1 commit,
5 years ago
1 file
+
16
−
0
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
content/guides/submitting_jobs/submitting_cuda_or_openacc_jobs.md
+
16
−
0
Options
@@ -94,3 +94,19 @@ module load cuda/8.0 compiler/pgi/16
./acc-app.exe
{{
<
/
highlight
>
}}
{{% /panel %}}
### Submitting Pre-emptable Jobs
Some GPU hardware is reserved by various groups for priority access. While the group that has
purchased the priority access will always have immediate access, HCC makes these nodes
available opportunistically. When not otherwise utilized,
**
jobs can run on these resources with the
limitation that they may be pre-empted (i.e. killed) at any time
**
.
To submit jobs to these resources, add the following to your srun or sbatch command:
{{
<
highlight
batch
>
}}
--partition=guest_gpu --gres=gpu
{{
<
/
highlight
>
}}
**
In order to properly utilize pre-emptable resources, your job must be able to support
some type of checkpoint/resume functionality.
**
Loading