|
1)
Message boards :
Number crunching :
Tasks won't finish...
(Message 1402)
Posted 11 Jul 2019 by hsdecalc Post: Same here: http://yafu.myfirewall.org/yafu/workunit.php?wuid=3918217 I'm number seven of this paket. Running endless since days. Last lines: 07/11/19 20:00:38 v1.34.5 @ CRUNCHER, nfs: previous data file found - commencing search for last special-q 07/11/19 20:00:49 v1.34.5 @ CRUNCHER, nfs: parsing special-q from .dat file 07/11/19 20:00:49 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c117: 191226036716312529204612193243490612051058835202779446558915418869961129767376387041998602418100041559534005184448597 07/11/19 20:00:49 v1.34.5 @ CRUNCHER, nfs: resuming with filtering 07/11/19 20:00:49 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 6 threads Aborting now, time limit reached. A lot of waste time. |
|
2)
Message boards :
Number crunching :
WU 9 days over deadline
(Message 843)
Posted 27 Apr 2016 by hsdecalc Post: I check the running WU as follows: - Open file factor.log from folder Boinc\slots\nn - check if new lines are generated at regular intervals - check taskmanager, details, if programs active with filename like: gnfs-lasieve4I13e.exe. The Boinc Function "Show Graphic" show you the type of sequence. If it is a Open End then it take a long time to find the next number. When the job is finished I check the factordb.com for the new result. Sample of factor.log: ... 04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323 04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: commencing poly selection with 4 threads 04/27/16 14:24:30 v1.34.5 @ CRUNCHER, nfs: setting deadline of 8047 seconds 04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: completed 32 ranges of size 250 in 7958.5150 seconds 04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: best poly = # norm 5.506486e-012 alpha -7.112219 e 1.450e-010 rroots 3 04/27/16 16:37:08 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 16:53:09 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 17:09:19 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, **************************** 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, Starting factorization of 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, using pretesting plan: normal 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, no tune info: using qs/gnfs crossover of 95 digits 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, **************************** 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: previous data file found - commencing search for last special-q 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: parsing special-q from .dat file 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: resuming with filtering 04/27/16 17:37:45 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 17:53:33 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 18:08:40 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 18:24:16 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 18:40:11 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 18:56:06 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 19:12:18 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, **************************** 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, Starting factorization of 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, using pretesting plan: normal 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, no tune info: using qs/gnfs crossover of 95 digits 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, **************************** 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: previous data file found - commencing search for last special-q 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: parsing special-q from .dat file 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: commencing nfs on c126: 521622676708542983109237724110101200655768213087042334643072769232764085149608182975748703464227023791340020676553772627767323 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: resuming with filtering 04/27/16 19:26:06 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 19:42:07 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads 04/27/16 19:58:36 v1.34.5 @ CRUNCHER, nfs: commencing lattice sieving with 4 threads.... |
|
3)
Message boards :
Number crunching :
why does it need all 8 cores to run
(Message 832)
Posted 5 Apr 2016 by hsdecalc Post: I see the same effect. But I think, it is because of short running tasks. The ecm.exe runs between 3-15 sec and it comes to overlap. I use following settings: <app_config> <app_version> <app_name>yafu</app_name> <plan_class>mt</plan_class> <avg_ncpus>4.0</avg_ncpus> <max_ncpus>4.0</max_ncpus> <cmdline>--nthreads 4</cmdline> </app_version> <app_version> <app_name>yafu-low</app_name> <plan_class>mt</plan_class> <avg_ncpus>4.0</avg_ncpus> <max_ncpus>4.0</max_ncpus> <cmdline>--nthreads 4</cmdline> </app_version> <project_max_concurrent>1</project_max_concurrent> </app_config> project_max_concurrent limited the project to start only one job/Wu. One job is using 4 cpus. I can follow the progress in factor.log. |