Too long calculation for the Sierpinski/Riesel Bases - long
log in

Advanced search

Message boards : Number crunching : Too long calculation for the Sierpinski/Riesel Bases - long

Previous · 1 · 2
Author Message
Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 3214
Credit: 22,879,153
RAC: 15
Message 2188 - Posted: 16 Dec 2015, 19:30:20 UTC - in response to Message 2187.

...
Did they run to 100% or have they been finished earlier?
...

I can answer it myself now, they end somewhere between 95.5% and 95.8% - I finished all 6 before a second one had been sent out and it gave my RAC temporarily a nice boost :-)


You can easily check the line in stderr.txt in slot directory, find this line:

8*800^914450-1, bit: 50000 / 8818828 [0.56%]. Time per bit: 34.238 ms.


Calculate 8818828 * 34.238 ms / 1000

and you have a nearly good end result in runtime. This can only be used on windows hosts.

Ananas
Send message
Joined: 26 Nov 15
Posts: 10
Credit: 370,238
RAC: 0
Message 2191 - Posted: 16 Dec 2015, 21:58:17 UTC - in response to Message 2188.
Last modified: 16 Dec 2015, 21:58:58 UTC

Thanks, I will use that formula next time to fight my (not the core client's) deadline panic :-)

Ananas
Send message
Joined: 26 Nov 15
Posts: 10
Credit: 370,238
RAC: 0
Message 2222 - Posted: 29 Dec 2015, 8:22:53 UTC - in response to Message 2188.
Last modified: 29 Dec 2015, 8:35:20 UTC

...
You can easily check the line in stderr.txt in slot directory, find this line:

8*800^914450-1, bit: 50000 / 8818828 [0.56%]. Time per bit: 34.238 ms.

...

The last stderr line seems to be even more interesting (taken from an active run) :

    8*800^951038-1, bit: 8250000 / 9171677 [89.95%]. Time per bit: 34.432 ms.


BoincView shows only somewhat more than 60.5% (in yellow, my color setting for "will miss deadline")

p.s.: If the wrapper could read that value, it could report that one to the core client. That's how the RNA wrapper does it - unfortunately the RNA applications don't have such a linear loop characteristic so the values are still not too exact there. Even though I do know the expected numbers of loops exactly, the progress line is not straight.

Ananas
Send message
Joined: 26 Nov 15
Posts: 10
Credit: 370,238
RAC: 0
Message 2241 - Posted: 2 Jan 2016, 18:44:28 UTC - in response to Message 2222.

...
    8*800^951038-1, bit: 8250000 / 9171677 [89.95%]. Time per bit: 34.432 ms.

...


It is getting harder to keep the deadline ...

    8*800^973840-1, bit: 50000 / 9391576 [0.53%]. Time per bit: 41.762 ms.
    8*800^973840-1, bit: 100000 / 9391576 [1.06%]. Time per bit: 40.380 ms.
    ...
    8*800^973840-1, bit: 3250000 / 9391576 [34.60%]. Time per bit: 40.744 ms.
    8*800^973840-1, bit: 3300000 / 9391576 [35.13%]. Time per bit: 147.026 ms. <= oops!
    8*800^973840-1, bit: 3350000 / 9391576 [35.67%]. Time per bit: 40.288 ms.
    ...
    8*800^973840-1, bit: 7100000 / 9391576 [75.59%]. Time per bit: 41.622 ms.
    8*800^973840-1, bit: 7150000 / 9391576 [76.13%]. Time per bit: 41.693 ms.

same computer, 20% longer processing time/bit

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 3214
Credit: 22,879,153
RAC: 15
Message 2242 - Posted: 2 Jan 2016, 18:55:34 UTC - in response to Message 2241.
Last modified: 2 Jan 2016, 18:56:30 UTC

...
    8*800^951038-1, bit: 8250000 / 9171677 [89.95%]. Time per bit: 34.432 ms.

...


It is getting harder to keep the deadline ...

    8*800^973840-1, bit: 50000 / 9391576 [0.53%]. Time per bit: 41.762 ms.
    8*800^973840-1, bit: 100000 / 9391576 [1.06%]. Time per bit: 40.380 ms.
    ...
    8*800^973840-1, bit: 3250000 / 9391576 [34.60%]. Time per bit: 40.744 ms.
    8*800^973840-1, bit: 3300000 / 9391576 [35.13%]. Time per bit: 147.026 ms. <= oops!
    8*800^973840-1, bit: 3350000 / 9391576 [35.67%]. Time per bit: 40.288 ms.
    ...
    8*800^973840-1, bit: 7100000 / 9391576 [75.59%]. Time per bit: 41.622 ms.
    8*800^973840-1, bit: 7150000 / 9391576 [76.13%]. Time per bit: 41.693 ms.

same computer, 20% longer processing time/bit



Its better to disable HT. --> runtime ~392210s

Ananas
Send message
Joined: 26 Nov 15
Posts: 10
Credit: 370,238
RAC: 0
Message 2243 - Posted: 2 Jan 2016, 19:02:34 UTC - in response to Message 2242.

...
Its better to disable HT. --> runtime ~392210s

But only 8 concurrent tasks then instead of 16, overall that would be a loss.

I guess I need an AVX machine some day :-/

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 3214
Credit: 22,879,153
RAC: 15
Message 2244 - Posted: 2 Jan 2016, 19:04:04 UTC - in response to Message 2243.
Last modified: 2 Jan 2016, 19:07:24 UTC

...
Its better to disable HT. --> runtime ~392210s

But only 8 concurrent tasks then instead of 16, overall that would be a loss.

I guess I need an AVX machine some day :-/


Yes, I have a good CPU but only AVX + OC, AVX2 is 20-40% faster with no OC :(

morgan
Send message
Joined: 1 Dec 14
Posts: 6
Credit: 7,276,066
RAC: 9,902
Message 2285 - Posted: 19 Jan 2016, 10:25:26 UTC

Name R800_900k-1M_wu_1843_4
Workunit 95082944
Created 15 Jan 2016, 2:29:37 UTC
Sent 15 Jan 2016, 4:34:43 UTC
Report deadline 19 Jan 2016, 4:34:43 UTC
Received 19 Jan 2016, 10:10:05 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 1238
Run time 2 days 16 hours 9 min 25 sec
CPU time 2 days 11 hours 37 min 4 sec
Validate state Task was reported too late to validate
Credit 0.00
Device peak FLOPS 2.34 GFLOPS
Application version Sierpinski / Riesel Base - long v0.05

Ish :-(

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 3214
Credit: 22,879,153
RAC: 15
Message 2286 - Posted: 19 Jan 2016, 17:46:15 UTC - in response to Message 2285.

Name R800_900k-1M_wu_1843_4
Workunit 95082944
Created 15 Jan 2016, 2:29:37 UTC
Sent 15 Jan 2016, 4:34:43 UTC
Report deadline 19 Jan 2016, 4:34:43 UTC
Received 19 Jan 2016, 10:10:05 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 1238
Run time 2 days 16 hours 9 min 25 sec
CPU time 2 days 11 hours 37 min 4 sec
Validate state Task was reported too late to validate
Credit 0.00
Device peak FLOPS 2.34 GFLOPS
Application version Sierpinski / Riesel Base - long v0.05

Ish :-(


You have a 4 day deadline + as long as the second result came back you have a valid result too.

Previous · 1 · 2
Post to thread

Message boards : Number crunching : Too long calculation for the Sierpinski/Riesel Bases - long


Main page · Your account · Message boards


Copyright © 2014-2017 BOINC Confederation / rebirther