+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: Modified SETI MB CUDA + opt AP package for full GPU utilization  (Read 154625 times)

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #210 on: 15 Jan 2009, 01:23:22 pm »
See you all 20 January I hope, good luck with crunching!

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #211 on: 15 Jan 2009, 07:10:37 pm »
Ok, just an update. I finished my first VLAR (0.123395) using Raistmer's V-6 package. It started at 13:56 and ended at 16:26. 2.5 hours almost exactly. The tasks page shows 346.90 seconds.My wingman showed 7,493.92 seconds for his. I claimed 80.53 credits he claimed 69.08. Both validated, credit issued 69.08 still not bad for only 2.5 hours.

For those that haven't been paying attention, I'm running a Celeron C2D with a GeForce 8500GT graphics card

Zoran Kirsic

  • Guest
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #212 on: 16 Jan 2009, 04:23:20 am »
Secondary link for Raistmer_s_opt_package_V6.rar

For the people who had problems with activation mail.

Offline efmer (fred)

  • Alpha Tester
  • Knight o' The Round Table
  • ***
  • Posts: 147
    • efmer
TThrottle Keep your temperatures controlled.
BoincTasks The best way to view BOINC

Offline Slawek

  • Knight o' The Realm
  • **
  • Posts: 55
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #214 on: 16 Jan 2009, 01:05:14 pm »
i cant download any CUDA WU now:(

And i cant testing new build

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #215 on: 16 Jan 2009, 02:21:49 pm »
yes, only app crashes ...

Offline Slawek

  • Knight o' The Realm
  • **
  • Posts: 55
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #216 on: 16 Jan 2009, 03:38:45 pm »
new versions APP better performance to ? or only stability etc ?

Maik

  • Guest
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #217 on: 16 Jan 2009, 09:33:16 pm »
was testing v6 on my 9600GT:
 - AR: 0.11437
 - runtime: 2086s
 - no crash/BSOD/stuck
 - referece: non LAR/VLAR needs around 1500-1600 sec

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #218 on: 17 Jan 2009, 08:18:23 am »
Just to throw another observation into the mix, after munching through a few WUs now.  I seem to be claiming ~30% more credits than AKv8 wingmen. So far these have all been denied.

Maik

  • Guest
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #219 on: 17 Jan 2009, 08:29:32 am »
Do you mean that?

Cuda owned by CPU ?!?

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #220 on: 17 Jan 2009, 08:31:37 am »
Yes, Maybe I'll have to find out if the flop [Actually fpop] counting standard is modified and build new AK_v8 builds...  :P

Posted in that thread:
Quote
It is 'counting' more flops [Well more correctly fpops anyway] for the same processing. This would not be tolerated in a third party app. I will have to determine if this is an intentional modification to the stock op count regime, so build new AK_v8 builds to match, if it continues.
« Last Edit: 17 Jan 2009, 08:48:12 am by Jason G »

Offline efmer (fred)

  • Alpha Tester
  • Knight o' The Round Table
  • ***
  • Posts: 147
    • efmer
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #221 on: 17 Jan 2009, 08:58:02 am »
Just to throw another observation into the mix, after munching through a few WUs now.  I seem to be claiming ~30% more credits than AKv8 wingmen. So far these have all been denied.
Maybe machine dependent I claim 13.83 the other non CUDA claims 16.58 so I claim a lot less....
But others are ok I claim 14.45 the other non CUDA claims 14.73.
I claim 59.82 the other 43.79
This one is interesting http://setiathome.berkeley.edu/workunit.php?wuid=394719892
It is a regular, a CUDA Raistmer and a stock CUDA. The Raistmer and Stock CUDA both claim more than a regular.
TThrottle Keep your temperatures controlled.
BoincTasks The best way to view BOINC

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #222 on: 17 Jan 2009, 09:00:40 am »
Yeah, If the count is borked it likely will vary by angle range in discrepancy.  My concern is that it gives, for some people, a false indication of performance. [On the other hand, if it is on purpose, then it becomes the new standard, to which optimised apps must then comply]
« Last Edit: 17 Jan 2009, 09:05:16 am by Jason G »

Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: Modified SETI MB CUDA + opt AP package for full GPU utilization
« Reply #223 on: 17 Jan 2009, 07:02:43 pm »
Yeah, If the count is borked it likely will vary by angle range in discrepancy.  My concern is that it gives, for some people, a false indication of performance. [On the other hand, if it is on purpose, then it becomes the new standard, to which optimised apps must then comply]

The undercount for triplets is recognized in a comment and is due to the CPU not knowing how many samples were above the triplet threshold in a PoT array. The overcount for gaussians is more complex, there's an overcount for the equivalent of getFixedPoT() which could easily be fixed, then difficulty in estimating how often the two data-dependent early outs are taken. A bit of statistical analysis on sufficient results should allow reasonable adjustments, though not exact. Probably the right target would be a small overclaim so variations seldom cause a lower claim than CPU and reduce the granted amount.
                                                                          Joe

Radiohead

  • Guest

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59559
Total Topics: 1672
Most Online Today: 652
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 614
Total: 614
Powered by EzPortal