I’ve tried to use the demo sample ‘nbody’ for stress GPU with the Xavier DevKit. but it will response as below show.
# ./nbody -fp64 -numbodies=1024
Run "nbody -benchmark [-numbodies=<numBodies>]" to measure performance.
-fullscreen (run n-body simulation in fullscreen mode)
-fp64 (use double precision floating point values for simulation)
-hostmem (stores simulation data in host memory)
-benchmark (run benchmark to measure performance)
-numbodies=<N> (number of bodies (>= 1) to run in simulation)
-device=<d> (where d=0,1,2.... for the CUDA device to use)
-numdevices=<i> (where i=(number of CUDA devices > 0) to use for simulation)
-compare (compares simulation results running once on the default GPU and once on the CPU)
-cpu (run n-body simulation on the CPU)
-tipsy=<file.bin> (load a tipsy model file for simulation)
NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.
> Windowed mode
> Simulation data stored in video memory
> Double precision floating point simulation
> 1 Devices used for simulation
freeglut (./nbody): failed to open display ':0'
Is there any configure/setting I missing? or any other utility you guys suggest for the GPU’s validate/stress?
Suppose you tried to run this sample via ssh.
The sample requires a DISPLAY device, please set the environment first.
:0 for output.
$ export DISPLAY=:0
Actually, I’m use the debug UART, it still not work even add the environment “DISPLAY=:0”( Even I add it via UART/ssh). Would you mind to share me which meaning about the :0?
Do you have a physical display connected to the Jetson?
The command will use
:0 as output (showing the nbody result).
In some cases, the physical display will mount to
Could you try the following command to see if it works?
$ export DISPLAY=:1
Yes, there is a HDMI cable connected to the Jetson Xaiver DevKit.
there is the screenshot with DISPLAY=:1 and it could work well
But, we’re wonder “Is that possible to run the nbody with console?” or any other utility to stress/validate CPU/GPU with console. Because there might no enough monitor for production validate.
It is still fail so far with console even we export the same environment as below show.
It is a rendering sample so it requires a display as output.
A workaround is to simulate a display device with some virtual display library.
It seems need time to study/implement it for me.
Is there any other utility could instead of nbody?
we just need a utility to stress cpu/gpu without monitor.
Please try if you can set up the virtual display environment with xvfb.
$ sudo apt-get install xvfb
$ Xvfb :1 &
$ export DISPLAY=:1
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.