I’ve tried to use the demo sample ‘nbody’ for stress GPU with the Xavier DevKit. but it will response as below show.
# pwd
/usr/local/cuda-10.2/samples/5_Simulations/nbody
# ./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?
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?
Thanks.
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 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.