View Single Post
Old 06-20-10, 08:49 AM   #99
gio___
Registered User
 
Join Date: Nov 2009
Posts: 44
Default Re: 260GTX nvidia-drivers-190.42-r3 - powermizer issue

Quote:
Originally Posted by cjb View Post
Thanks - I'm interested in the FDTD3d example myself; something like

./FDTD3d --dimx=144 --dimy=144 --dimz=144

for which I get:

gtx260m - 284 MPoints/s
gt240 - 754 MPoints/s
c1060 - 1909 MPoints/s

The gtx260m should really be close to the gt240. This one's not a sterling benchmark either, but it's fairly close...
./FDTD3d --dimx=144 --dimy=144 --dimz=144
./FDTD3d Starting...

Set-up, based upon target device GMEM size...
getTargetDeviceGlobalMemSize
cudaGetDeviceCount
cudaGetDeviceProperties
calloc host_output
malloc input
malloc coeff
generateRandomData

FDTD on 144 x 144 x 144 volume with symmetric filter radius 4 for 5 timesteps...

fdtdReference...
calloc intermediate
Host FDTD loop
t = 0
t = 1
t = 2
t = 3
t = 4

fdtdReference complete
calloc device_output
fdtdGPU...
cudaGetDeviceCount
cudaSetDevice (device 0)
cudaMalloc bufferOut
cudaMalloc bufferIn
set block size to 16x16
cudaMemcpy (HostToDevice) bufferIn
cudaMemcpy (HostToDevice) bufferOut
cudaMemcpyToSymbol (HostToDevice) stencil
cudaEventCreate
cudaEventCreate
GPU FDTD loop
t = 0 launch kernel
t = 1 launch kernel
t = 2 launch kernel
t = 3 launch kernel
t = 4 launch kernel

cudaThreadSynchronize
cudaMemcpy (DeviceToHost)
cudaEventElapsedTime

FDTD3d, Throughput = 179030.9718 MPoints/s, Time = 0.00002 s, Size = 2820096 Points, NumDevsUsed = 1, Blocksize = 256
gio___ is offline   Reply With Quote