log in |
1)
Message boards :
Number crunching :
Something has changed in SRBase
(Message 8152)
Posted 21 Mar 2022 by UBT - Timbo Historically, the completion time for Base, Short and Average tasks was typically about 2 hours. The Task Progress increased at a consistent rate from 0% to 100%. I've had exactly the same issue on a number of "Riesel Base - short v0.22" CPU tasks, which I received during the recent Formula BOINC Sprint. Many of these tasks did complete, but I had a number that got stuck at 100% after 8 hours...and this was on a 4-core Windows x64 PC. And such was the lack of progress, I've had to abort many tasks (before the deadline), as I just knew the PCs would not process these other tasks before their deadline....even though my "cache" using BOINC Manager was set to 0.5+0.5 days... Somehow SRBase is allowing more tasks to download, as it is using an inaccurate "Time to completion" for each task - estimates were around 24 minutes, but actual time is between 9,000 and 14,000 seconds (2.5 to 3.9 HOURS). error msgs for 3 of these tasks: Name R703_250-300k_wu_19075_0 Workunit 70607562 after 29,238.85 seconds Stderr output Name R703_250-300k_wu_19078_0 Workunit 70607565 after 31,919.33 seconds
Name R703_250-300k_wu_18879_0 Workunit 70607366 after 28,989.31 seconds (8+ hours) [quote]Stderr output <core_client_version>7.16.20</core_client_version> <![CDATA[ <message> aborted by user</message> <stderr_txt> 14:46:25 (8936): wrapper (7.5.26012): starting 14:46:25 (8936): wrapper: running llr.exe ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) Base factorized as : 19*37 Base prime factor(s) taken : 37 Starting N+1 prime test of 494*703^268972-1 Using zero-padded FFT length 448K, Pass1=448, Pass2=1K, a = 3 494*703^268972-1, bit: 50000 / 2543780 [1.96%]. Time per bit: 15.066 ms. 494*703^268972-1, bit: 100000 / 2543780 [3.93%]. Time per bit: 16.988 ms. 494*703^268972-1, bit: 150000 / 2543780 [5.89%]. Time per bit: 13.458 ms. 494*703^268972-1, bit: 200000 / 2543780 [7.86%]. Time per bit: 15.213 ms. 494*703^268972-1, bit: 250000 / 2543780 [9.82%]. Time per bit: 11.652 ms. 494*703^268972-1, bit: 300000 / 2543780 [11.79%]. Time per bit: 14.904 ms. 494*703^268972-1, bit: 350000 / 2543780 [13.75%]. Time per bit: 11.022 ms. 494*703^268972-1, bit: 400000 / 2543780 [15.72%]. Time per bit: 12.506 ms. 494*703^268972-1, bit: 450000 / 2543780 [17.69%]. Time per bit: 11.886 ms. 494*703^268972-1, bit: 500000 / 2543780 [19.65%]. Time per bit: 12.464 ms. 494*703^268972-1, bit: 550000 / 2543780 [21.62%]. Time per bit: 16.945 ms. 494*703^268972-1, bit: 600000 / 2543780 [23.58%]. Time per bit: 15.245 ms. 494*703^268972-1, bit: 650000 / 2543780 [25.55%]. Time per bit: 11.889 ms. 494*703^268972-1, bit: 700000 / 2543780 [27.51%]. Time per bit: 14.020 ms. 494*703^268972-1, bit: 750000 / 2543780 [29.48%]. Time per bit: 17.374 ms. 494*703^268972-1, bit: 800000 / 2543780 [31.44%]. Time per bit: 23.795 ms. 494*703^268972-1, bit: 850000 / 2543780 [33.41%]. Time per bit: 18.197 ms. 494*703^268972-1, bit: 900000 / 2543780 [35.38%]. Time per bit: 14.267 ms. 494*703^268972-1, bit: 950000 / 2543780 [37.34%]. Time per bit: 24.296 ms. 494*703^268972-1, bit: 1000000 / 2543780 [39.31%]. Time per bit: 19.856 ms. 494*703^268972-1, bit: 1050000 / 2543780 [41.27%]. Time per bit: 9.323 ms. 494*703^268972-1, bit: 1100000 / 2543780 [43.24%]. Time per bit: 14.670 ms. 494*703^268972-1, bit: 1150000 / 2543780 [45.20%]. Time per bit: 17.432 ms. 494*703^268972-1, bit: 1200000 / 2543780 [47.17%]. Time per bit: 20.501 ms. 494*703^268972-1, bit: 1250000 / 2543780 [49.13%]. Time per bit: 15.702 ms. 494*703^268972-1, bit: 1300000 / 2543780 [51.10%]. Time per bit: 12.189 ms. 494*703^268972-1, bit: 1350000 / 2543780 [53.07%]. Time per bit: 9.402 ms. 494*703^268972-1, bit: 1400000 / 2543780 [55.03%]. Time per bit: 16.164 ms. 494*703^268972-1, bit: 1450000 / 2543780 [57.00%]. Time per bit: 15.948 ms. 494*703^268972-1, bit: 1500000 / 2543780 [58.96%]. Time per bit: 12.368 ms. 494*703^268972-1, bit: 1550000 / 2543780 [60.93%]. Time per bit: 14.206 ms. 494*703^268972-1, bit: 1600000 / 2543780 [62.89%]. Time per bit: 12.777 ms. 494*703^268972-1, bit: 1650000 / 2543780 [64.86%]. Time per bit: 16.550 ms. 494*703^268972-1, bit: 1700000 / 2543780 [66.82%]. Time per bit: 19.832 ms. 494*703^268972-1, bit: 1750000 / 2543780 [68.79%]. Time per bit: 22.443 ms. 494*703^268972-1, bit: 1800000 / 2543780 [70.76%]. Time per bit: 20.650 ms. 494*703^268972-1, bit: 1850000 / 2543780 [72.72%]. Time per bit: 14.442 ms. </stderr_txt> ]]> {/quote] In all 3 cases, the stderr.txt files (in the slot diretories) were still being written to, until just before the task was aborted...which implies the tasks were still being crunched... regards Tim |
2)
Message boards :
Number crunching :
Stuck at 100%
(Message 1454)
Posted 21 May 2015 by UBT - Timbo Then another program has grabbed all the power. Hi Reb, Unfortunately, that's not the case - this particular PC *only* crunches BOINC - no other programs run on it. So, there must be another answer? I'll see what happens when the next tasks download and see what happens...thus far the short WU's are being crunched OK, and until the other day, the average WU's were OK too... regards Tim |
3)
Message boards :
Number crunching :
Stuck at 100%
(Message 1448)
Posted 21 May 2015 by UBT - Timbo The GPU is the problem. It needs a full CPU core so it can slow down the calculations. You dont need more RAM, a WU is taking around 65MB. If you run more than one project check the RAM usage, BU can take a lot. Hi Reb, But I set the BOINC Manager preferences to only use 75% of the CPU's available. So, only 3 are used...not 4. That means the GPU has full access to one CPU core, and I can then run some CPU tasks, plus some ASIC's. I'll will reduce the CPU preference to (say) 30% and see if any more SRBase tasks complete OK. regards Tim |
4)
Message boards :
Number crunching :
Stuck at 100%
(Message 1441)
Posted 19 May 2015 by UBT - Timbo finish file present too long Hi Reb, Thanks for your reply. OK, so this is a quad-core Intel-CPU PC, running Win 7 (x64) with 2 Gb RAM and 400 Gb of free space on the HDD. Task manager shows lots of spare CPU capacity and very little paging to the hard drive. Otherwise, it only runs BU (via ASIC's) and WU-Prop - that's it - it's a dedicated BOINC machine.....with 3 cores dedicated to CPU tasks. Plus, there's a GPU running Moo. How can it need more "resources" than this, to give to SRBase? Do I need more RAM, because that's the only thing that I can do to "upgrade" this PC? regards Tim |
5)
Message boards :
Number crunching :
Stuck at 100%
(Message 1439)
Posted 19 May 2015 by UBT - Timbo Application Sierpinski/Riesel Base - long 0.04. Latest BOINC Manager 7.4.42 (x64), running on Windows 7. Hi all, I just had this same issue - 2 WU's at 100% and "Waiting to run"..... In the meantime other project tasks started.....so, when I saw this I suspended these other tasks and BM re-started the SRBase WU's...but within seconds, both WU's were "Computation error"...so that's 4+ hours wasted. http://srbase.myfirewall.org/sr5/result.php?resultid=34818320 http://srbase.myfirewall.org/sr5/result.php?resultid=34818184 These are both "Sierpinski / Riesel Base - average v0.04" WU's. I haven't had this issue before, so do not know the reason - PC has been working fine before now: http://srbase.myfirewall.org/sr5/results.php?userid=327&offset=0&show_names=0&state=4&appid=13 regards Tim |