Posts by Beyond

21) Message boards : Number crunching : Stuck at 100% for nearly 6 days !! (Message 1131)
Posted 20 Feb 2018 by Profile Beyond
Post:
Let it run!
You will get credits up to 5 days after the deadline.
Gnfs is the Number Field Sieve. Means all other methods failed to factor this composite completely. So, now the long running gnfs has to factor it.

In this message it says 10 days. Has that changed?

https://yafu.myfirewall.org/yafu/forum_thread.php?id=255&postid=1013#1013
22) Message boards : Number crunching : Diffrence between app "YAFU 134.05 (mt)" and app "YAFU-4t 134.05 (4t)" (Message 1124)
Posted 16 Feb 2018 by Profile Beyond
Post:
Thanks, sorry for all the questions. Trying to learn how Yafu works as it's a little different than most projects. I'm liking it.
23) Message boards : Number crunching : Diffrence between app "YAFU 134.05 (mt)" and app "YAFU-4t 134.05 (4t)" (Message 1122)
Posted 16 Feb 2018 by Profile Beyond
Post:
Yoyo, thanks for this info, very helpful. BTW, do you want us to tell you when WUs are running overtime? I have one that's going overtime now but still updating so I know it's progressing (so far 47.9 hours). The one behind it hasn't started but will be overtime in a few minutes. It's not a slow machine either.

Edit: They both just finished. The 2nd one was very short. Still though do you want us to let you know about overtime WUs if they're still updating?
24) Message boards : Number crunching : How do I get YAFU to stop sending me tasks that use up 100% of my cores? (Message 1119)
Posted 15 Feb 2018 by Profile Beyond
Post:
Thanks again. Trying some BOINC configs to try to allow 16t...
25) Message boards : Number crunching : How do I get YAFU to stop sending me tasks that use up 100% of my cores? (Message 1117)
Posted 15 Feb 2018 by Profile Beyond
Post:
Thanks. Question, if I have a machine that allows 15 cores to be used, can it get 16t and 32t tasks? So far haven't seen any.
26) Message boards : Number crunching : Error: Can't link app version file (Message 1115)
Posted 14 Feb 2018 by Profile Beyond
Post:
Malwarebytes is a fine program but use the free non-active version and scan for malware manually.
27) Message boards : Number crunching : How do I get YAFU to stop sending me tasks that use up 100% of my cores? (Message 1114)
Posted 13 Feb 2018 by Profile Beyond
Post:
Hello,

4t and 8t tasks uses 4 and 8 cores. But all otheres use as much cores as available. You can select only the 16t tasks in your settings and all cores are used. I would appreciate if more users run the 16t.

yoyo

Hi yoyo! Is there a post somewhere that explains how this all works in excruciating, painstaking detail for those of us who are mentally challenged?
Best Regards/Beyond
28) Message boards : Number crunching : 1/10th RAC for Similar CPUs (Message 1113)
Posted 13 Feb 2018 by Profile Beyond
Post:
The project uses the standard Boinc out of the box "creditNew" credit system because YAFU is a test project to test newest Boinc server versions.

This "creditNew" needs some time to adjust.

The original code name was "we hate you so we're going to make your life miserable" but since that was too long, David changed it to "creditnew". ;-)
29) Message boards : Number crunching : So how long is your C116 Task? (Message 746)
Posted 26 Nov 2014 by Profile Beyond
Post:
I'm talking about runtimes:

2 core machine:

233906	233906	9780	Completed and validated   44,623.90	5,365.19	4,744.74   YAFU v134.01 (mt)

Longer runtime, 4 core, faster machine (running 3 cores), 1/26th of the credit:

235322	235322	9569	Completed and validated   45,438.71	21,268.38	180.60	   YAFU v134.01 (mt)


Example 2, 3 identical machines:

239586	239586	9780	Completed and validated   84,372.99	12,292.74	2,787.18   YAFU v134.01 (mt)

239579	239579	9571	Completed and validated   92,866.80	12,787.03	673.78	   YAFU v134.01 (mt)

237997	237997	9570	Completed and validated   91,559.31	12,914.54	576.07 	   YAFU v134.01 (mt)
30) Message boards : Number crunching : So how long is your C116 Task? (Message 744)
Posted 26 Nov 2014 by Profile Beyond
Post:
Creditnew is bizarre. Three identical machines, scoring for same length WUs as much as 8x difference, actually sometimes more. Have no idea why.
31) Message boards : Number crunching : So how long is your C116 Task? (Message 739)
Posted 22 Nov 2014 by Profile Beyond
Post:
No, when I saw it had aborted I looked in the slot dir and it was empty. The disk has 34GB free. I looked at the slot dir about an hour earlier and still the only files updating were the 2 mentioned above. On all my other Yafu WUs there are a number of files that update perhaps every 10 minutes. Also. what's the maximum ram the yafu app uses?
32) Message boards : Number crunching : So how long is your C116 Task? (Message 737)
Posted 22 Nov 2014 by Profile Beyond
Post:
I paused it to let 2 other yafu WUs run that were approaching deadline. Restarted it a few hours ago and just now it aborted with a computation error (196):

11-22-14 08:04 Aborting task yafu_C101_F1416456605_312_0: exceeded disk limit

From Stderr:

<core_client_version>7.4.27</core_client_version>
<![CDATA[
<message>
Maximum disk usage exceeded
</message>
<stderr_txt>
al yield: 6034233, q=15083179 (0.00956 sec/rel)

http://yafu.myfirewall.org/yafu/result.php?resultid=237720
33) Message boards : Number crunching : So how long is your C116 Task? (Message 735)
Posted 21 Nov 2014 by Profile Beyond
Post:
Now I have one on a different machine that's been sitting at 100% for hours. It's till using 100% CPU on 2 cores. The only files updating since yesterday are .last_spq0 and .last_spq1 which update every minute. Everything else in the slot directory is about 20 hours old. Kill it or keep running it?
34) Message boards : Number crunching : So how long is your C116 Task? (Message 734)
Posted 20 Nov 2014 by Profile Beyond
Post:
Aborted. Thanks yoyo!
35) Message boards : Number crunching : So how long is your C116 Task? (Message 732)
Posted 19 Nov 2014 by Profile Beyond
Post:
The nfs.dat in the slot directory is only 116,000K and hasn't been updated since 11/14. I suppose it's dead. I was assuming that it was still running because of the BOINC progress percentage and since the Yafu task still shows as using 50% of the CPU in task manager. I just paused the WU. Do you want the nfs.dat sent to you?
36) Message boards : Number crunching : So how long is your C116 Task? (Message 730)
Posted 19 Nov 2014 by Profile Beyond
Post:
Hi yoyo,

I have a WU that's been running for 132 hours and has been at 100% for the last 2 days:

http://yafu.myfirewall.org/yafu/workunit.php?wuid=227630

It's on a slow 2 core Ivy Bridge box, but the longest previous WU on this machine was 21.3 hours. Should I leave it run or is it dead? It's still using CPU, but looks like only 1 core.

It seemed to run fairly normally at first, but then as the completion percentage got higher it went slower and slower. just before hitting 100% it was progressing at about 0.001% per 2 hours.

Edit: Here's the output from a log file if that helps.:

11/13/14 22:13:02 v1.34.5 @ SUBA,
11/13/14 22:13:02 v1.34.5 @ SUBA, ****************************
11/13/14 22:13:02 v1.34.5 @ SUBA, Starting factorization of 47987412564198200109186934880570980526987301425001440780338916116510420217531104751755815639270422743607663313229559
11/13/14 22:13:02 v1.34.5 @ SUBA, using pretesting plan: normal
11/13/14 22:13:02 v1.34.5 @ SUBA, no tune info: using qs/gnfs crossover of 95 digits
11/13/14 22:13:02 v1.34.5 @ SUBA, ****************************
11/13/14 22:13:02 v1.34.5 @ SUBA, rho: x^2 + 3, starting 1000 iterations on C116
11/13/14 22:13:02 v1.34.5 @ SUBA, rho: x^2 + 2, starting 1000 iterations on C116
11/13/14 22:13:02 v1.34.5 @ SUBA, rho: x^2 + 1, starting 1000 iterations on C116
11/13/14 22:13:02 v1.34.5 @ SUBA, pm1: starting B1 = 150K, B2 = gmp-ecm default on C116
11/13/14 22:13:02 v1.34.5 @ SUBA, current ECM pretesting depth: 0.00
11/13/14 22:13:02 v1.34.5 @ SUBA, scheduled 30 curves at B1=2000 toward target pretesting depth of 35.69
11/13/14 22:13:02 v1.34.5 @ SUBA, Finished 30 curves using Lenstra ECM method on C116 input, B1=2K, B2=gmp-ecm default
11/13/14 22:13:02 v1.34.5 @ SUBA, current ECM pretesting depth: 15.18
11/13/14 22:13:02 v1.34.5 @ SUBA, scheduled 74 curves at B1=11000 toward target pretesting depth of 35.69
11/13/14 22:13:10 v1.34.5 @ SUBA, Finished 74 curves using Lenstra ECM method on C116 input, B1=11K, B2=gmp-ecm default
11/13/14 22:13:10 v1.34.5 @ SUBA, current ECM pretesting depth: 20.24
11/13/14 22:13:10 v1.34.5 @ SUBA, scheduled 214 curves at B1=50000 toward target pretesting depth of 35.69
11/13/14 22:14:23 v1.34.5 @ SUBA, Finished 214 curves using Lenstra ECM method on C116 input, B1=50K, B2=gmp-ecm default
11/13/14 22:14:23 v1.34.5 @ SUBA, pm1: starting B1 = 3750K, B2 = gmp-ecm default on C116
11/13/14 22:14:26 v1.34.5 @ SUBA, current ECM pretesting depth: 25.33
11/13/14 22:14:26 v1.34.5 @ SUBA, scheduled 430 curves at B1=250000 toward target pretesting depth of 35.69
11/13/14 22:22:14 v1.34.5 @ SUBA, Finished 430 curves using Lenstra ECM method on C116 input, B1=250K, B2=gmp-ecm default
11/13/14 22:22:14 v1.34.5 @ SUBA, pm1: starting B1 = 15M, B2 = gmp-ecm default on C116
11/13/14 22:22:25 v1.34.5 @ SUBA, current ECM pretesting depth: 30.45
11/13/14 22:22:25 v1.34.5 @ SUBA, scheduled 904 curves at B1=1000000 toward target pretesting depth of 35.69
11/13/14 23:24:54 v1.34.5 @ SUBA, Finished 904 curves using Lenstra ECM method on C116 input, B1=1M, B2=gmp-ecm default
11/13/14 23:24:54 v1.34.5 @ SUBA, current ECM pretesting depth: 35.56
11/13/14 23:24:54 v1.34.5 @ SUBA, scheduled 66 curves at B1=3000000 toward target pretesting depth of 35.69
11/13/14 23:37:18 v1.34.5 @ SUBA, Finished 66 curves using Lenstra ECM method on C116 input, B1=3M, B2=gmp-ecm default
11/13/14 23:37:18 v1.34.5 @ SUBA, final ECM pretested depth: 35.70
11/13/14 23:37:18 v1.34.5 @ SUBA, scheduler: switching to sieve method
11/13/14 23:37:18 v1.34.5 @ SUBA, nfs: commencing nfs on c116: 47987412564198200109186934880570980526987301425001440780338916116510420217531104751755815639270422743607663313229559
11/13/14 23:37:18 v1.34.5 @ SUBA, nfs: commencing poly selection with 2 threads
11/13/14 23:37:18 v1.34.5 @ SUBA, nfs: setting deadline of 4050 seconds
11/14/14 00:44:48 v1.34.5 @ SUBA, nfs: completed 54 ranges of size 250 in 4050.3227 seconds
11/14/14 00:44:48 v1.34.5 @ SUBA, nfs: best poly = # norm 5.194789e-011 alpha -5.928782 e 5.000e-010 rroots 3
11/14/14 00:44:48 v1.34.5 @ SUBA, nfs: commencing lattice sieving with 2 threads
11/14/14 01:31:26 v1.34.5 @ SUBA, nfs: commencing lattice sieving with 2 threads
11/14/14 02:16:38 v1.34.5 @ SUBA, nfs: commencing lattice sieving with 2 threads
11/14/14 02:59:16 v1.34.5 @ SUBA, nfs: commencing lattice sieving with 2 threads


Previous 20



Datenschutz / Privacy Copyright © 2011-2024 Rechenkraft.net e.V. & yoyo