+- +-
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: CPU <-> GPU rebranding  (Read 204962 times)

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #255 on: 28 Oct 2009, 11:23:45 am »
I'm stumped for now, but will think about it some more.
                                                                              Joe
Just some more info
1) now on both hosts I have installed Boinc Manager 6.6.41
2) on the host receiving only 5.28 I run boincview.exe and (sometimes) BoincTasks.
This last one can manage Day Work and Wanted WU .... so I think that can be involved in the problem
In any case I have not filled those fields with data.
FF


Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: CPU <-> GPU rebranding
« Reply #256 on: 28 Oct 2009, 02:21:34 pm »
The primary server-side change is that the Scheduler now tells the client to use what it considers the "best" app version. What it considers "best" doesn't consider the version number. Instead it just takes the suitable app versions in order, and chooses the one with the highest flops rating. If the flops are equal, the first suitable app is considered "best".

It's possible that simply listing the higher numbered version first in the app_info.xml would help, but that doesn't explain why the current order works on some hosts but not others.

Franz, with 6.6.x you could consider editing in flops settings for the apps, making 6.03 slightly higher than 5.28. That seems like it should correct the situation. MarkJ's app_info for AP503, AP505, MB603 and MB608 thread should provide enough detail if you decide to try that.
                                                                                    Joe

Offline Richard Haselgrove

  • Messenger Pigeon
  • Knight who says 'Ni!'
  • *****
  • Posts: 2819
Re: CPU <-> GPU rebranding
« Reply #257 on: 28 Oct 2009, 03:32:31 pm »

The primary server-side change is that the Scheduler now tells the client to use what it considers the "best" app version. What it considers "best" doesn't consider the version number. Instead it just takes the suitable app versions in order, and chooses the one with the highest flops rating. If the flops are equal, the first suitable app is considered "best".


I wonder whether that explains the tendency for SETI to fill the CUDA cache before the CPU cache, in times of drought.

(Assuming your CUDA card is faster than your CPU, that is.)

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #258 on: 29 Oct 2009, 01:49:43 pm »
Franz, with 6.6.x you could consider editing in flops settings for the apps, making 6.03 slightly higher than 5.28. That seems like it should correct the situation. MarkJ's app_info for AP503, AP505, MB603 and MB608 thread should provide enough detail if you decide to try that.
                                                                                    Joe
mmmmmm mumbe mumble ... I don't like to change app_info ... but If I have to do it, I think that the better solution is to delete the 528 section .... isn't it?

So...

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>


What do you think?

Franz

Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: CPU <-> GPU rebranding
« Reply #259 on: 29 Oct 2009, 02:17:00 pm »
mmmmmm mumbe mumble ... I don't like to change app_info ... but If I have to do it, I think that the better solution is to delete the 528 section .... isn't it?

So...

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>


What do you think?

Franz

Finish and report any already downloaded work which has been already assigned to 5.28 first, or BOINC will trash it. Other users might be grateful to get the reissues, but with the project having very little new work to deliver your host might be idle for awhile.
                                                                         Joe

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #260 on: 29 Oct 2009, 03:39:07 pm »
Finish and report any already downloaded work which has been already assigned to 5.28 first, or BOINC will trash it. Other users might be grateful to get the reissues, but with the project having very little new work to deliver your host might be idle for awhile.
                                                                         Joe
Yes, of course. You are right.
But if I stop new work now, I will finish CUDA work in one day, while CPU buffer in 6/7 days.
May be I leave all as now ...

Franz

Sutaru Tsureku

  • Guest
Re: CPU <-> GPU rebranding
« Reply #261 on: 18 Nov 2009, 04:46:52 pm »
I'm not up-to-date..

Is a Reschedule_prog in work, which can reschedule WUs at SETI@home BETA ?

This would be nice!

Thanks!

Sutaru Tsureku

  • Guest
Re: CPU <-> GPU rebranding
« Reply #262 on: 18 Nov 2009, 04:54:08 pm »
Ahh.. BTW..

Maybe it's possible to extend the DL area with the Reschedule_prog?

Then more people would see it (advertising for free), easier to DL and used more.

 :)

Offline Pepi

  • Knight o' The Realm
  • **
  • Posts: 119
Re: CPU <-> GPU rebranding
« Reply #263 on: 20 Nov 2009, 03:12:32 pm »
How to put back WHAR from CPU to GPU? Once it transferred from GPU to CPU it cannot be rescheduled for cuda?

valterc

  • Guest
Re: CPU <-> GPU rebranding
« Reply #264 on: 25 Nov 2009, 07:05:48 am »
Hi all, I tested rescheduler and found the following problem:

boinc is attached to seti and primegrid, after running rescheduler something wrong happened to all my primegrid workunits. These simply disappeared. Eventually these (at least some) come back after awhile (resending lost results)...

I don't know if rescheduler can be used in a "mixed" environemnt...
Any hints?

Offline hiamps

  • Knight o' The Round Table
  • ***
  • Posts: 126
    • Swans Candles and Supplies
Re: CPU <-> GPU rebranding
« Reply #265 on: 26 Nov 2009, 04:33:08 pm »
I am sorry I did not read every message but could someone tell me what my "Boinc Main Path" is supposed to be? Everything I put in there it says doesn't exist. I am using Windows 7, Can't seem to set up rescheduler.

Error:C:\BOINC\boinc.exe does not exist.
Error:C:\BOINC\projects\setiathome.berkeley.edu\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\boinc.exe does not exist.
Error:C:\ProgramData\BOINC\projects\boinc.exe does not exist


EDIT
Weird, when I use the rescheduler to find the path boinc isn't in there. When I just opened explore it is...C:\Program Files\BOINC . Then the path to C:\ProgramData\BOINC wouldn't show up so I had to copy and paste it also using explorer. I have show all files checked also. It worked.
« Last Edit: 26 Nov 2009, 05:08:19 pm by hiamps »

Offline Claggy

  • Alpha Tester
  • Knight who says 'Ni!'
  • ***
  • Posts: 3111
    • My computers at Seti Beta
Re: CPU <-> GPU rebranding
« Reply #266 on: 26 Nov 2009, 04:44:39 pm »
The default directory where BOINC will install its executables to is:
Windows 32bit: C:\PROGRAM FILES\BOINC\
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC\

The Big BOINC 6 Answer Thread.

Claggy

Offline corsair

  • Knight o' The Realm
  • **
  • Posts: 112
Re: CPU <-> GPU rebranding
« Reply #267 on: 26 Nov 2009, 06:05:56 pm »
The default directory where BOINC will install its executables to is:
Windows 32bit: C:\PROGRAM FILES\BOINC\
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC\

The Big BOINC 6 Answer Thread.

Claggy

Not completely agreed, if you're in windows x32 absolutely agree.

if you're in windows x64 there are two options:
1 - setup BOINC x32 and the install path will be  C:\PROGRAM FILES (x86)\BOINC\
2 - setup BOINC x64 (the proper option) the install path wil be  C:\PROGRAM FILES\BOINC\
Over the sailors' graves never groves grass.

Cheers all / Corsair.

Sutaru Tsureku

  • Guest
Re: CPU <-> GPU rebranding
« Reply #268 on: 28 Nov 2009, 09:13:29 pm »
Hmm.. no ReSchedule 2.0 for SETI@home BETA:-\

Or I missed something, ReSchedule 1.9 work also with SETI@home BETA?
Not for me..  ;)

It would be nice, so I wouldn't lose much performance if I would test the stock_MB_6.09_CUDA23_app at SETI@home BETA.
Or it's also needed to test this app with VLARs?
I guess - this VLAR prob will be to the time until the nVIDIA devs would be jump in, or?
So current it's not needed to test VLARs?

Sutaru Tsureku

  • Guest
Re: CPU <-> GPU rebranding
« Reply #269 on: 28 Nov 2009, 09:26:14 pm »
@ Pepi

AFAIK, you can reschedule CPU-GPU and GPU-CPU back and forward.
Like you want.
I make all the time only VLARs to CPU, all WUs to GPU.
With 100 % to GPU.

Maybe, I guess.. if you make less, maybe 50 % - the prog make VLARs to CPU and split all other WUs to CPU (- the VLARs) and GPU.
There are also some check boxes, maybe with this?

@ valterc

I don't use ReSchedule in AUTO mode.
I close/exit BOINC. Start ReSchedule, execute it. Close/exit ReSchedule and start again BOINC.
Everything fine.
Maybe this work also for you with more projects.

 

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: 167
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 152
Total: 152
Powered by EzPortal