Forum > GPU crunching

BOINC 6.10.x (Alpha) For Windows

<< < (5/6) > >>

Raistmer:
Yes, it's very annoying to lose work w/o any good reason to do that!

<core_client_version>6.10.12</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>

Claggy:

--- Quote from: Arnulf on 10 Oct 2009, 03:47:29 am ---Hello Claggy!

Can you tell me if there is some coding that errors out WU's that runs for more than 24 hours?
I have tested the 6.10.12 version and that one reports errors when running over 86430 seconds.
When re-installing 6.10.3 the errors goes away.

Arnulf

Here are the results:

http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321437
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321435
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321436
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321243

--- End quote ---

Have you got FLOPS values entered in your app_info?

Boinc 6.10.5 introduced:

- client: if app_info.xml doesn't specify flops, use an estimate that takes GPUs into account.

If you do have an app_info with flops values, the flops value is too high, as Boinc will abort the WU when it gets to 10x the WU flops value,

If you don't have flops values in an app_info, then Boinc will take the GPU estimated flops, and expect the WU to be finished very quickly,

In changeset 19282, which should be in the next new version of Boinc:

- client: if anonymous platform description (app_info.xml)

doesn't specify FLOPS for a GPU app,
assume that it runs at CPU peak speed rather than GPU peak speed.
Better to be conservative, otherwise job might be aborted
due to time limit exceeded.

Since you seem to be running Raistmer's AstroPulse hybrid CPU/ATI GPU build for GPUs with double precision support  and a lot of it runs on the CPU,
best way round this if you want to run Boinc 6.10.5 to 6.10.13 is to add CPU flops values to the GPU part of the app info.

References:

Error code -171 to -180 explained.

Infinite loops

Claggy

Arnulf:
Thanks!

<flops>4127010920</flops>

How do I determine what number to insert? The line above I snagged from a CUDA App_info.xml.
I have also found some formula that says GFLOPS*0.2 but thats for CUDA devices, and I expect Brook to be somewhat different.

My Boinc manager says my card should deliver 428GFLOPS.

Arnulf

Claggy:
This post is the Bible for setting up a app_info's flop values to try and equalise DCF and work fetch between CPU and GPU's:

app_info for AP503, AP505, MB603 and MB608

If you take your GPU flops you get:

428 000 000 000 * 0.2 = 85 600 000 000

and CPU flops:

    1 824 240 000 * 2.6 =  4 743 024 000

I'd eithier take the CPU flops * 2.6 and use that,
Or I'd take the GPU flops *0.2, and take a digit off the end,

so

4 743 024 000

or

8 560 000 000

The first one will be more safe, the second one will give you better work fetch,
I don't know how fast Raistmer's AP/Brook app is, so it'll be a case of suck it and see,
you can always increase the flops values later.

Claggy

Raistmer:
Good estimate is ~24% faster in CPU time than current opt AP release.
Elapsed time difference is less though.

Navigation

[0] Message Index

[#] Next page

[*] Previous page