------------
Running app : AK_v8b_win_SSE41.exe with -verb -nog
with WU : 03dc08ad.15767.890.15.8.213.wu
Started at : 20:20:54.402
Ended at : 20:56:35.543
2141.047 secs Elapsed
2128.016 secs CPU time
Result : stored as ref for validation.
------------
Running app : setiathome_6.05_windows_intelx86__cuda.exe with -verb -st
with WU : 03dc08ad.15767.890.15.8.213.wu
Started at : 20:56:35.590
Ended at : 21:22:04.605
1528.969 secs Elapsed
95.953 secs CPU time
Speedup : 95.49%
Ratio : 22.18 x
----- R1:R2 ------ ----- R2:R1 ------
Good Bad Ugly Good Bad Ugly
Spike 2 0 0 2 0 0
Gaussian 2 0 0 2 0 0
Pulse 1 0 0 1 0 0
Triplet 1 0 1 1 0 0
Best Spike 1 0 0 1 0 0
Best Gaussian 1 0 0 1 0 0
Best Pulse 1 0 0 1 0 0
Best Triplet 0 0 1 0 0 1
---- ---- ---- ---- ---- ----
9 0 2 9 0 1
Result : Weakly similar.
VLAR AR~0.15
Errors at CUDA mem copy, invalid results.
Wall clock execution time greater than for CPU app.
============
AK_v8_win_SSSE3x.exe -verb -st / 23no08ad.15915.22976.9.8.127.wu :
Started at : 19:48:10.591
Ended at : 19:48:55.394
44.772 secs Elapsed
44.757 secs CPU time
...
No heartbeat from core client for 30 sec - exiting
...
MB_6.06r380mod_CUDA | AK_v8_win_SSE41 | setiathome_6.06_windows_intelx86__cuda | ||
Spike count: 0 | Spike count: 9 | Spike count: 0 | ||
Pulse count: 0 | Pulse count: 0 | Pulse count: 0 | ||
Triplet count: 31 | Triplet count: 2 | Triplet count: 31 | ||
Gaussian count: 0 | Gaussian count: 0 | Gaussian count: 0 |
A new error for you all to have fun with...
cudaAcc_find_triplets doesn't support more than MAX_TRIPLETS_ABOVE_THRESHOLD numBinsAboveThreshold in find_triplets_kernel
http://setiathome.berkeley.edu/result.php?resultid=1112071921
I didn't do stand alone testing due to my pc locked up every time I tried to....
It's all true if it would be show in CPU result too. While we have such error in GPU only I tend to think it's just another CUDA app problem....
-MB_6.06r380mod_CUDA.exe -> task (WinTaskManager) goes stuck, after 30 sec i kicked them
'--> no video-errors.
...unknown CUDA error in stderr....
It's all true if it would be show in CPU result too. While we have such error in GPU only I tend to think it's just another CUDA app problem....
In this case it looks like a design choice rather than an execution bug. My guess is someone did a mathematical estimation of the most "above threshold" points which should occur in pure random data and allowed for somewhat more. It looks like another case where ideal randomness isn't quite achieved...
Joe
Sure, they used the same CUDA as I did ;)...unknown CUDA error in stderr....
Oooh, that sounds familiar :P