rsnt_translations
53,464
edits
Visualization: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
No edit summary |
(Marked this version for translation) |
||
| Line 113: | Line 113: | ||
</tabs> | </tabs> | ||
=== Remote off-screen windows via Xvfb === | === Remote off-screen windows via Xvfb === <!--T:176--> | ||
<!--T:177--> | |||
Some applications insist on displaying graphical output, but you don't actually need to see them since the results are saved in a file. | Some applications insist on displaying graphical output, but you don't actually need to see them since the results are saved in a file. | ||
In that case the job can run as a regular batch job, using either the CPU or the GPU for 3D rendering. To enable this you can run | In that case the job can run as a regular batch job, using either the CPU or the GPU for 3D rendering. To enable this you can run | ||
the application you are calling with the X virtual frame buffer (Xvfb) in a job script as follows: | the application you are calling with the X virtual frame buffer (Xvfb) in a job script as follows: | ||
xvfb-run <name-of-application> | <!--T:178--> | ||
xvfb-run <name-of-application> | |||
<!--T:179--> | |||
if using the CPU for rendering or | if using the CPU for rendering or | ||
xvfb-run vglrun -d egl <name-of-application> | <!--T:180--> | ||
xvfb-run vglrun -d egl <name-of-application> | |||
<!--T:181--> | |||
if using the GPU for rendering, in which case you need to reserve one GPU with Slurm, see [[Using_GPUs_with_Slurm|Using GPUs with Slurm]]. | if using the GPU for rendering, in which case you need to reserve one GPU with Slurm, see [[Using_GPUs_with_Slurm|Using GPUs with Slurm]]. | ||
Note that, depending on the workload the GPU may not necessarily be faster than the CPU, so it's important to benchmark before | Note that, depending on the workload the GPU may not necessarily be faster than the CPU, so it's important to benchmark before | ||