Donate To Seti@HomeSeti@Home optimized science apps and information
 
Welcome, Guest. Please login or register.
25 May 2013, 07:51:45 pm

Login with username, password and session length
 
» Home
» Forums
» Downloads
» FAQ
» News

» Search site
 
 
 
If you've registered already but never got your activation email, please click here.
 
 
Seti@Home optimized science apps and information  |  Optimized Seti@Home apps  |  Windows  |  GPU crunching  |  Topic: CPU <-> GPU rebranding 0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] 2 3 ... 25 Go Down Print
Author Topic: CPU <-> GPU rebranding  (Read 80959 times)
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



CPU <-> GPU rebranding
« on: 07 May 2009, 04:06:03 pm »

Attached script will move VLAR and VHAR tasks to CPU and midrange tasks to GPU queues.
This increase host productivity.
With small modifications it can be used to move all (or almost all) MB tasks to GPU and vice-versa.
It should be run from BOINC data directory.
Don't forget to backup you BOINC data folder and disable BOINC network access on first script use.

* CPU_GPU_rebrand_V2.rar (0.84 KB - downloaded 423 times.)
« Last Edit: 12 Jul 2009, 03:32:21 pm by Raistmer » Logged
M_M
Squire
*
Offline Offline

Posts: 29


Re: CPU <-> GPU rebranding perl script
« Reply #1 on: 08 May 2009, 11:52:37 am »

Thanks for the script.

I have also noticed that it does not seem to be working when there are some other boinc projects besides seti@home... it's trying to find other project WUs in seti work directory and ofcourse it fails...

Could you please fix this, so it searches and try to fix only seti WUs. I guess it shouldn't be so complicated.

Thanks in advance.

Logged
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



Re: CPU <-> GPU rebranding perl script
« Reply #2 on: 08 May 2009, 03:25:06 pm »

Yes, it will try find SETI beta tasks in SETI project too.
Logged
Lord Asmodeus
Guest


Email
Re: CPU <-> GPU rebranding perl script
« Reply #3 on: 09 May 2009, 02:57:06 am »

Hello. I'd like to use this script but I have no idea as the how to (use a script in general). I found an explanation for ubuntu but i'm on XP. I found elsewhere than it doesn't work with more than 500 WU, is it true (I have more than a thousand currently) ?

Thanks
Logged
M_M
Squire
*
Offline Offline

Posts: 29


Re: CPU <-> GPU rebranding perl script
« Reply #4 on: 09 May 2009, 03:04:25 am »

You need a perl interpreter for windows, like activeperl or some other windows distribution.

http://win32.perl.org/wiki/index.php?title=Main_Page
Logged
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



Re: CPU <-> GPU rebranding perl script
« Reply #5 on: 09 May 2009, 04:35:08 pm »

If you have >500 MB tasks in cache script will exit w/o modifying BOINC state.
It's some kind of foolproof. There are too many users now who trash whole 10-day cache with few thousands tasks with easy trying some new software/configurations w/o any care of properly backing up their BOINC installation.
Anyone who skilled enough can easely modify this limit. The rest of users should obey it.
Logged
Lord Asmodeus
Guest


Email
Re: CPU <-> GPU rebranding perl script
« Reply #6 on: 09 May 2009, 06:29:12 pm »

OK, it is quite simple...but I have a problem  Cry

I modified the limit, that was simple. I run it, and it doesn't work :

Quote
>perl -w CPU_GPU_rebrand_V2.pl

Number of CPU tasks before rescheduling:0
Number of GPU tasks before rescheduling:610
Illegal division by zero at CPU_GPU_rebrand_V2.pl line 50.

I studied the script, and the div/0 is logical with all the tasks considered as GPU. I don't understand why this is the case, however.

btw, thank you for your previous answers, I have learned something.
Logged
Leopoldo
Guest


Email
Re: CPU <-> GPU rebranding perl script
« Reply #7 on: 12 May 2009, 12:10:16 pm »

Attached script will move VLAR and VHAR tasks to CPU and midrange tasks to GPU queues.
...
Don't forget to backup you BOINC data folder and disable BOINC network access on first script use.

BTW, is it too hard to convert VisualBasic6-program into VBScript?
In the beginning I did rebranding 608->603 manually, but after increasing of VLAR-WUs quantity I made VB6-program and using it past days...
Logged
M_M
Squire
*
Offline Offline

Posts: 29


Re: CPU <-> GPU rebranding perl script
« Reply #8 on: 17 May 2009, 06:24:32 am »

OK, it is quite simple...but I have a problem  Cry

I modified the limit, that was simple. I run it, and it doesn't work :

Quote
>perl -w CPU_GPU_rebrand_V2.pl

Number of CPU tasks before rescheduling:0
Number of GPU tasks before rescheduling:610
Illegal division by zero at CPU_GPU_rebrand_V2.pl line 50.

I studied the script, and the div/0 is logical with all the tasks considered as GPU. I don't understand why this is the case, however.

btw, thank you for your previous answers, I have learned something.


I have exactly the same problem. Sad     Using Boinc 6.6.20, and having a Q9650 and GTX260.

Having a lot of CPU AP tasks, and probably no 603 CPU tasks, only 6.08 GPU ones (from which some of them are VLARs to be rebranded for sure).

Logged
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



Re: CPU <-> GPU rebranding perl script
« Reply #9 on: 17 May 2009, 06:47:38 am »

Here replacement script.

* CPU_GPU_rebrand_V3.rar (1.91 KB - downloaded 214 times.)
Logged
M_M
Squire
*
Offline Offline

Posts: 29


Re: CPU <-> GPU rebranding perl script
« Reply #10 on: 17 May 2009, 08:50:31 am »

Thanks, just used V3 script which rebranded 86 GPU to CPU units.

But I think I also came accross a serious bug. Before applying the script, I had a couple of AP WUs, some of them half-done, which now dissapeared... Sad
Logged
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



Re: CPU <-> GPU rebranding perl script
« Reply #11 on: 17 May 2009, 08:57:31 am »

Thanks, just used V3 script which rebranded 86 GPU to CPU units.

But I think I also came accross a serious bug. Before applying the script, I had a couple of AP WUs, some of them half-done, which now dissapeared... Sad
Will look at this issue. For now you should restore from backup.
Logged
Lord Asmodeus
Guest


Email
Re: CPU <-> GPU rebranding perl script
« Reply #12 on: 17 May 2009, 02:56:46 pm »

It seems OK for me (I don't participate in AP).

Quote
C:\Documents and Settings\All Users\Application Data\BOINC>CPU_GPU_rebrand_V3.pl

Number of CPU tasks before rescheduling:0
Number of GPU tasks before rescheduling:1882
Number of CPU tasks after rescheduling:508
Number of GPU tasks after rescheduling:1374

I'ill let it work in "no network mode" for tonight to confirm the success.
Logged
Raistmer
Working Code Wizard
Volunteer Developer
Knight who says 'Ni!'
*****
Online Online

Posts: 11043



Re: CPU <-> GPU rebranding perl script
« Reply #13 on: 17 May 2009, 03:38:21 pm »

Thanks, just used V3 script which rebranded 86 GPU to CPU units.

But I think I also came accross a serious bug. Before applying the script, I had a couple of AP WUs, some of them half-done, which now dissapeared... Sad
Try this one.
I have no AP tasks so can't check if it will work as intendedbut hope it will.
Backup before first use required as usual.

* CPU_GPU_rebrand_V4.rar (1.93 KB - downloaded 206 times.)
Logged
EPG
Guest


Email
Re: CPU <-> GPU rebranding perl script
« Reply #14 on: 17 May 2009, 05:28:04 pm »

Not good, still kills ap wus in the second WHILE loop if i understand correctly.
I think the wu check should be based on the <app_name>seti... instead of !<name>ap,
because that would be compatible with any other project.

<result>
    <name>ap_12mr09ad_B4_P0_00220_20090517_09656.wu_1</name>
    <final_cpu_time>0.000000</final_cpu_time>
    <final_elapsed_time>0.000000</final_elapsed_time>
    <exit_status>0</exit_status>
    <state>2</state>
    <platform>windows_intelx86</platform>
    <fpops_cumulative>588532400000000.000000</fpops_cumulative>
    <wu_name>ap_12mr09ad_B4_P0_00220_20090517_09656.wu</wu_name>
    <report_deadline>1245152434.000000</report_deadline>
    <file_ref>
        <file_name>ap_12mr09ad_B4_P0_00220_20090517_09656.wu_1_0</file_name>
        <open_name>pulse.out</open_name>
    </file_ref>
    <version_num>608</version_num>
    <plan_class>cuda</plan_class>

</result>
« Last Edit: 18 May 2009, 04:44:23 am by EPG » Logged
Pages: [1] 2 3 ... 25 Go Up Print 
Seti@Home optimized science apps and information  |  Optimized Seti@Home apps  |  Windows  |  GPU crunching  |  Topic: CPU <-> GPU rebranding « previous next »
Jump to:  


Quote!
If everything seems to be going well, you have obviously overlooked something.
- Murphy's Law

 
Site Statistics
Total Members:91
Total Posts:51,177
Total Topics:1,433
Downloads
..Some PHP stuff ToDo
Pages served
Today:4,615
Total:17,341,225
(since 6/26/2006)
Latest Member:
[seti.international] Philip J. Fry
 
 
Seti@Home optimized science apps and information | Powered by Enigma 2.0 (RC1).
© 2003-2013, LSP Dev Team. All Rights Reserved.
Seti@Home optimized science apps and information Forums | Powered by SMF.
© 2005, Simple Machines LLC. All Rights Reserved.
Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS!