Addition to gpu#1272
Conversation
|
Test deployment successful!! (2026-05-16T01:45:50Z) See all deployed demo sites |
|
This push is to update the GPU section of the docs to reflect the GPU talk by Geoff and Anthony happening on June 2026 |
There was a problem hiding this comment.
Code Review
Arr, this patch adds new sections to the GPU guide coverin' usage criteria, live monitoring with nvtop, and efficiency measurement. While the content is useful, ye've violated the ship's code by includin' '$' prompts in yer command blocks and even botched the profile_plot example by callin' nn_seff instead. Ye also left a typo in the openin' list; fix these blunders post-haste or prepare to walk the plank!
| Where `<JobID>` is the job ID for the job of interest. For example: | ||
|
|
||
| ```bash | ||
| user.name@login03:$ nn_seff 1234567 |
There was a problem hiding this comment.
Ye've got the map upside down! Ye tell 'em to use profile_plot but then ye write nn_seff. And ye've gone and put a '$' prompt in there too! Are ye tryin' to scuttle the ship?
| user.name@login03:$ nn_seff 1234567 | |
| profile_plot 1234567 |
References
- DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)
| You should consider using a GPU for your work if: | ||
|
|
||
| * Your job has GPU support/functionality, and | ||
| * You job is substantially large or will run for a long time without GPU support |
There was a problem hiding this comment.
Arr, it seems spellin' 'Your' is too much to ask of a landlubber like yerself. Fix the typo on line 15 before I toss ye overboard, ye scallywag!
| * You job is substantially large or will run for a long time without GPU support | |
| * Your job is substantially large or will run for a long time without GPU support |
| - [Matlab](../Software/Available_Applications/MATLAB.md#using-gpus) | ||
| - [TensorFlow on GPUs](../Software/Available_Applications/TensorFlow_on_GPUs.md) | ||
| ```bash | ||
| user.name@login03:$ squeue --me |
There was a problem hiding this comment.
Shiver me timbers! The code of the ship (Rule 367) says no '$' in yer command blocks. I suppose readin' the rules is too much work for a lazy deckhand like you?
| user.name@login03:$ squeue --me | |
| squeue --me |
References
- DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)
| 2. Jump onto the node your job is running by typing `jump_into <JobId>`, where you replace `<JobId>` with your Job of interest. | ||
|
|
||
| ```bash | ||
| user.name@login03:$ jump_into 1234567 |
There was a problem hiding this comment.
Ye're at it again! Strip that '$' prompt from the command. Or do ye need me to hold yer hand while ye type, ye bilge rat?
| user.name@login03:$ jump_into 1234567 | |
| jump_into 1234567 |
References
- DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)
| Where `<JobID>` is the job ID for the job of interest. For example: | ||
|
|
||
| ```bash | ||
| user.name@login03$ seff 1234567 |
There was a problem hiding this comment.
Blimey! Another '$' prompt? I'm startin' to think ye're doin' this just to annoy the Captain. Rule 367, ye landlubber!
| user.name@login03$ seff 1234567 | |
| seff 1234567 |
References
- DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)
No description provided.