+- +-
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 234284 times)

Offline Marius

  • Knight o' The Realm
  • **
  • Posts: 84
Re: CPU <-> GPU rebranding
« Reply #240 on: 13 Sep 2009, 04:56:34 pm »

The first problem is still open.

Franz
Is rescheduler.exe able to "see" setiathome_enhanced 5.28?
Franz
No sorry, only the newer 6 series are supported.

Offline Marius

  • Knight o' The Realm
  • **
  • Posts: 84
Re: CPU <-> GPU rebranding
« Reply #241 on: 13 Sep 2009, 05:06:25 pm »
Quote from: samuel7
Are you still developing your tool?

Not really, the only thing left to do is to add seti beta support but i'm swamped in work the last months. There's very little time left for seti at this moment.

Quote from: samuel7
My client_state got truncated in the middle of another project's data when I ran it (v1.9) the other day. The rebranding itself went fine and no errors were reported. The only actual loss was the time spent on the tasks that were running at the time (because the <active_task_set> part was gone).
I'm sorry to hear that, this is very unusual as i'm locking all files and shutdown boinc (and wait for it to release the files). Is there any reason why it has done this?

Quote from: samuel7
I didn't want to revert to the backup because after restart BOINC fetched more MB tasks for the GPU. I should have realised something was wrong when it ran benchmarks but I just left it alone as I normally do. :-[

I have the before and after client_state files if you're interested.
The boinc servers are behaving poorly again so you are right to leave it alone. And yes, i'm interested in those files.

Greetings,
Marius

Samuel

  • Guest
Re: CPU <-> GPU rebranding
« Reply #242 on: 14 Sep 2009, 01:14:00 pm »
I'm sorry to hear that, this is very unusual as i'm locking all files and shutdown boinc (and wait for it to release the files). Is there any reason why it has done this?

I exit BOINC manually anyway. One additional symptom is that the test feature displays the WU counts correctly but says '0 slots occupied' when there are active MB tasks. I recently added PrimeGrid's PPS Sieve subproject and it seems ReSchedule can't parse beyond the first WU download URL. This:
    <url>http://www.primegrid.com/download/pps_sr2sieve_workunit_zz.php?from=958648&to=958649</url>
changes into this:
    <url></url></file_info></client_state> and EOF  :(
When I remove the PrimeGrid project data ReSchedule works fine.

And yes, i'm interested in those files.
If you still want them please PM me your email addy.

Offline Geek@Play

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 330
Re: CPU <-> GPU rebranding
« Reply #243 on: 14 Sep 2009, 07:16:54 pm »
Marius..........

I have seen several complaints about all the old client_state.xml files left behind when running your rebranding tool.  I persoally run rescheduler from a batch file and the first step command is "Del D:\BOINC\client_state2009*.xml" which removes any old client_state2009 files.

Can you make any changes that would remove the old files that are left behind by the rebranding?
Boinc....Boinc....Boinc....Boinc

rx780

  • Guest
Re: CPU <-> GPU rebranding
« Reply #244 on: 04 Oct 2009, 02:10:35 am »
So the client_state.xml2009* files are created when run rebrand without shutting down Boinc? These files can be safely deleted? (Assuming boinc shut down )

Offline MarkJ

  • Knight o' The Realm
  • **
  • Posts: 96
Re: CPU <-> GPU rebranding
« Reply #245 on: 04 Oct 2009, 05:29:17 am »
So the client_state.xml2009* files are created when run rebrand without shutting down Boinc? These files can be safely deleted? (Assuming boinc shut down )

You don't have to shut it down as long as you leave the original client_state and client_state_prev file alone.

The client_state yyyyymmdd ones are backup copies of client_state before Reschedule changes the wu information and BOINC doesn't use these.

timiman

  • Guest
Re: CPU <-> GPU rebranding
« Reply #246 on: 15 Oct 2009, 02:46:46 pm »
I agree. You dont know when you are going to need any previous client_state.xml file... :(

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #247 on: 24 Oct 2009, 03:45:55 pm »
I should like to know why I have two PCs, ... same cpu, os, boinc level, otopmized apps (using unified same installer), cuda (one 250 and other 260) but in one I get only 5.28 (so I can't use reschedule) and in the other I get only 6.03 (so I can use reschedule).
Tell me how I can get 6.03 (prayers, ...  mantra, ... software?)

FF

Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: CPU <-> GPU rebranding
« Reply #248 on: 25 Oct 2009, 02:52:47 pm »
I should like to know why I have two PCs, ... same cpu, os, boinc level, otopmized apps (using unified same installer), cuda (one 250 and other 260) but in one I get only 5.28 (so I can't use reschedule) and in the other I get only 6.03 (so I can use reschedule).
Tell me how I can get 6.03 (prayers, ...  mantra, ... software?)

FF

Add or fix the section in the app_info.xml file which says you have a 6.03 compliant application installed. The BOINC core client assigns CPU work to the highest numbered CPU application it knows about.

Post the app_info.xml here if you'd like more specific advice.
                                                                                Joe

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #249 on: 25 Oct 2009, 06:18:21 pm »
my app_info.xml must be the standard one, build by the last  lunatics unified installer.
what else?

Code: [Select]
<app_info>
-
<app>
<name>setiathome_enhanced</name>
</app>
-
<file_info>
<name>AK_v8b_win_SSSE3x.exe</name>
<executable/>
</file_info>
-
<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>
-
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
-
<file_ref>
<file_name>AK_v8b_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>astropulse_v5</name>
</app>
-
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
-
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
-
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>astropulse_v505</name>
</app>
-
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
-
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
-
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
-
<app>
<name>setiathome_enhanced</name>
</app>
-
<file_info>
<name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name>
<executable/>
</file_info>
-
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
-
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
-
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
-
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
-
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
-
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
-
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
-
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
-
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>



Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: CPU <-> GPU rebranding
« Reply #250 on: 26 Oct 2009, 04:55:21 pm »
my app_info.xml must be the standard one, build by the last  lunatics unified installer.
what else?
...

The "-" characters and unusual spacing are unwanted changes usually caused by some Microsoft "helpful" feature. If that only happened when you copied and pasted here there's no harm done, but if it's that way on disk it may be the cause of the problem. Check by opening it in Notepad or another plain text editor. If it's damaged, the simple solution would be to copy the file from the other similar host which is working correctly, the more thorough solution would be to uninstall and reinstall the optimized apps.

Assuming the file is good, it's hard to guess why BOINC 6.6.36 isn't doing what it should. Perhaps someone will recall a similar case with that version of BOINC. Incidentally, is it host 2979049 or host 2693912 which is stuck on 5.28?
                                                                                Joe

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #251 on: 26 Oct 2009, 05:23:33 pm »

The "-" characters and unusual spacing are unwanted changes usually caused by some Microsoft "helpful" feature. If that only happened when you copied and pasted here there's no harm done, but if it's that way on disk it may be the cause of the problem. Check by opening it in Notepad or another plain text editor. If it's damaged, the simple solution would be to copy the file from the other similar host which is working correctly, the more thorough solution would be to uninstall and reinstall the optimized apps.

Assuming the file is good, it's hard to guess why BOINC 6.6.36 isn't doing what it should. Perhaps someone will recall a similar case with that version of BOINC. Incidentally, is it host 2979049 or host 2693912 which is stuck on 5.28?
                                                                                Joe
I have reinstalled the the optimized apps just some hours before writing here.
I never edited app_info.xml  (it is the original from optimized apps installation in both cases)
The host with GTX 260 (2979049) is going fine. all 6.03
The host with GTS 250 (2693912) is affected by the 5.28 problem

Do you need more info?
FF

Franz

  • Guest
Re: CPU <-> GPU rebranding
« Reply #252 on: 27 Oct 2009, 12:41:16 pm »
I have reinstalled the the optimized apps just some hours before writing here.
I never edited app_info.xml  (it is the original from optimized apps installation in both cases)
The host with GTX 260 (2979049) is going fine. all 6.03
The host with GTS 250 (2693912) is affected by the 5.28 problem

Do you need more info?
FF
Just a quick controll, done with a file compare software.
app_info.xm in the two hosts are identical.
FF

Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: CPU <-> GPU rebranding
« Reply #253 on: 27 Oct 2009, 12:44:51 pm »
...
Assuming the file is good, it's hard to guess why BOINC 6.6.36 isn't doing what it should. Perhaps someone will recall a similar case with that version of BOINC. Incidentally, is it host 2979049 or host 2693912 which is stuck on 5.28?
                                                                                Joe

I have reinstalled the the optimized apps just some hours before writing here.
I never edited app_info.xml  (it is the original from optimized apps installation in both cases)
The host with GTX 260 (2979049) is going fine. all 6.03
The host with GTS 250 (2693912) is affected by the 5.28 problem

Do you need more info?
FF
Just a quick controll, done with a file compare software.
app_info.xm in the two hosts are identical.
FF

I'm stumped for now, but will think about it some more.
                                                                              Joe

Offline Richard Haselgrove

  • Messenger Pigeon
  • Knight who says 'Ni!'
  • *****
  • Posts: 2819
Re: CPU <-> GPU rebranding
« Reply #254 on: 27 Oct 2009, 02:19:06 pm »

I'm stumped for now, but will think about it some more.
                                                                              Joe

I have a machine in a similar state. The project is Einstein: there was a project Beta test of ABP1 v3.11

I have an app_info with a set of files, a 310 version block and a 311 version block (both referring to the same files). The host is crunching quite happily, but every new task is getting branded 310. I haven't done an exact byte-by-byte check, but it looks as if the 311 block is present and correct in both app_info.xml and client_state.xml, and both versions were listed in the latest sched_request to the project.

The strange thing is, this host is my old P4 Windows 2000 home server, running BOINC v5.10.13 - so completely unaffected by any recent BOINC developments. My other P4, my daily driver with a very similar app_info, is getting tasks branded 311 with the same version of BOINC.

So it rather seems it's the behaviour of the servers which has changed. Einstein has started limited (anonymous platform only) CUDA testing, so they must have updated their server code a bit - not that you'd know it from looking at their web pages, which haven't changed for a year or more - so I'm wondering if all the new <plan_class> code has undone the certainties like 'will assign highest version available' that we used to rely on.

 

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