GPU/CPU performance dependence from AR value

Forum > GPU crunching

<< < (4/6) > >>

Jason G:

--- Quote from: Raistmer on 19 Apr 2009, 11:24:12 am ---Do I understand right that only yellow lines should be changed for CPU<->GPU rebranding ?

--- End quote ---

Yes, pretty much. What I found easier (for me, while I was doing it manually) was to add an extra application name for cpu app with no plan class to app_info, say: setiathome_enhanced_AK version 608 , (Planclass CPU optional). This way all rebranded work shows as new version but CPU in manager. That was helpful in quickly identifying work that was already rebranded visually.

This way only the application name and plan class lines needed changing, rather than the version, and work already allocated to CPU via 6.03 was untouched. new work for CPU went to 6.03, new cuda work went to cuda 6.08, and only rebranded work was 6.08 (CPU plan class), meaning it was easy to recognise and undo if needed.

Raistmer:
I going to rebrand not only GPU to CPU but CPU to GPU too ;)
Now finishing current results running (for clean first test) and will try to do rebrand. produced file looks OK at my not very experienced in client_state.xml sight :)

Raistmer:
Unfortunately, it was not single place:
<workunit>
<name>01fe09aa.11349.15205.4.8.69</name>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<rsc_fpops_est>78856403871557.094000</rsc_fpops_est>
<rsc_fpops_bound>788564038715571.000000</rsc_fpops_bound>
<rsc_memory_bound>33554432.000000</rsc_memory_bound>
<rsc_disk_bound>33554432.000000</rsc_disk_bound>
<file_ref>
<file_name>01fe09aa.11349.15205.4.8.69</file_name>
<open_name>work_unit.sah</open_name>
</file_ref>
</workunit>

Here version number mentioned too.
I got errors on all rebranded tasks. Smth like can't link on result ....
19/04/2009 21:56:31 SETI@home [error] State file error: missing task
19/04/2009 21:56:31 SETI@home [error] Can't link task 01fe09aa.11349.15205.4.8.75_0 in state file

Richard Haselgrove:
Fred's script just replaces "608" with "603" in both the <workunit> and <result> sections (matching ones, of course), and deletes the <plan_class>cuda</plan_class> line completely - making it look exactly like a 603 directly allocated to the CPU by the server. That seems the simplest solution: but I'm intrigued by Josef's suggestion. That might be worth a look.

Richard Haselgrove:
Well, I've had a look through the Proxomitron docs, and I'm a bit daunted by the match/replace language. Does anyone have any experience of writing that sort of meta-character based filter? Here's an example of what we need to do.

--- Quote ---<rubbish>
...
</rubbish>
<file_info>
<name>27dc08ab.32733.481.6.8.9</name>
<url>http://boinc2.ssl.berkeley.edu/sah/download_fanout/f1/27dc08ab.32733.481.6.8.9</url>
<md5_cksum>d8bf53ae5251691603446976bd9e757d</md5_cksum>
<nbytes>375323</nbytes>
</file_info>
<workunit>
<rsc_fpops_est>23780000000000.000000</rsc_fpops_est>
<rsc_fpops_bound>237800000000000.000000</rsc_fpops_bound>
<rsc_memory_bound>33554432.000000</rsc_memory_bound>
<rsc_disk_bound>33554432.000000</rsc_disk_bound>
<name>27dc08ab.32733.481.6.8.9</name>
<app_name>setiathome_enhanced</app_name>
<file_ref>
<file_name>27dc08ab.32733.481.6.8.9</file_name>
<open_name>work_unit.sah</open_name>
</file_ref>
</workunit>
...
<file>
<WU>
<file>
<WU>
...
<file_info>
<name>27dc08ab.32733.481.6.8.9_1_0</name>
<generated_locally/>
<upload_when_present/>
<max_nbytes>65536</max_nbytes>
<url>http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler</url>
<xml_signature>
b849d6e0adcc332ad1601a97d75f4d073ea633ae16b00663e6aa98bac0477c08
3742e0330aae2deee62f2406ddcd1020b3ff02e3cf6f7f77482a97dbc453a489
21fe18199095dda88f172da2d97b1d1cddff23272c832be8e44ba10b38212700
0e5ff950052f3a870c850bb3efa7cefcee57ce02ddcb6473d55526a34ba2dc4f
.
</xml_signature>
</file_info>
<result>
<report_deadline>1240773971</report_deadline>
<wu_name>27dc08ab.32733.481.6.8.9</wu_name>
<name>27dc08ab.32733.481.6.8.9_1</name>
<file_ref>
<file_name>27dc08ab.32733.481.6.8.9_1_0</file_name>
<open_name>result.sah</open_name>
</file_ref>
<platform>windows_intelx86</platform>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
</result>
...
<file>
<result>
<file>
<result>
...
<rubbish>
...
</rubbish>
--- End quote ---

The <rubbish> and all the intervening file/workunit/file/result stuff needs preserving, of course.

But the process is:

Identify a WU for re-branding by <rsc_fpops_est> - this is a VHAR
Remember the next <name> for later use
Look for a matching <wu_name> (it only occurs in a <result> section)
Change the next following <version_num> from 608 to 603, or vice versa as desired
Delete or insert the <plan_class> line to match

allowing for up to 20 names to be matched and re-branded in a single sched_reply file. The process is very similar to Fred's surgery on client_state, so it could easily be scripted: but I'm not sure it could be pattern-matched on the fly.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version