gdalwarp primarily uses CPU & only briefly uses opencl, Nvidia V6.5 Toolkit
|Reported by:||SteeevO||Owned by:||warmerdam|
|Severity:||normal||Keywords:||cuda, opencl, gdalwarp,|
I'm on a new machine with linux mint 17.1 and a K420 Quadro card. I've built gdal from source enabling opencl and pointing the configure options to the header files included in the Nvidia Cuda Toolkit v6.5.
I was able to run and compile the CUDA samples that were included in the toolkit. the samples run fine and activity shows in nvidia-smi
However, when running gdalwarp, the processes is handled only on the CPU and the GPU remains untouched by gdal according to nvidia-smi and the gui system monitor.
using options like -multi -wo USE_ALL_CPUS -wo ENABLE_OPENCL=TRUE all have no effect on time to run the proccess.
Here is the config command I've been using: ./configure --with-png=internal --with-libtiff=internal --with-geotiff=internal --with-jpeg=internal --with-gif=internal --with-openjpeg=/home/steven/SourceBuilds/openjpeg-2.1.0-Darwin-i386 --with-opencl=yes --with-opencl-include=/usr/local/cuda-6.5/include
Here is the gdalwarp command that I've been using to test:
sudo time gdalwarp -tr 1 1 -t_srs '+proj=merc +a=635752.3142 +b=634752.3142 +lat_ts=0.0 +Lon_0=0.0 +x=0.00 +y_0=0 +k=1.0 +units=m +nadgrids=@null +wktext +no_defs' -multi -wo NUM_THREADS_ALL_CPUS -wo USE_OPENCL=TRUE -of gtiff -wm 6000 ~/SatImagery/35111/m_3511101_ne_12_1_20100609_20101018.jp2 ~/testout.tiff
Change History (11)
comment:9 by , 9 years ago
|Summary:||gdalwarp won't run on GPU with OpenCL enabled and Nvidia Cuda Toolkit 6.5 → gdalwarp primarily uses CPU & only briefly uses opencl, Nvidia V6.5 Toolkit|