|
1)
Message boards :
Number crunching :
So how long is your C116 Task?
(Message 726)
Posted 8 Oct 2014 by Bruce Kennedy Post: It may be using 1 thread but it has all 8 tied up and prevents other work from being done. I'm going to cancel it now, it's be running for 36 hours. |
|
2)
Message boards :
Number crunching :
So how long is your C116 Task?
(Message 724)
Posted 7 Oct 2014 by Bruce Kennedy Post: The C116 WU is now at 100% and waiting to run. Here are the contents of the text files in the slot directory. 10/05/14 22:50:24 v1.34.5 @ BRUCE, 10/05/14 22:50:24 v1.34.5 @ BRUCE, **************************** 10/05/14 22:50:24 v1.34.5 @ BRUCE, Starting factorization of 38248148288262939877592328434712626897417157843496786404118652121030605576532119227866057116701426977912061693502551 10/05/14 22:50:24 v1.34.5 @ BRUCE, using pretesting plan: normal 10/05/14 22:50:24 v1.34.5 @ BRUCE, no tune info: using qs/gnfs crossover of 95 digits 10/05/14 22:50:24 v1.34.5 @ BRUCE, **************************** 10/05/14 22:50:24 v1.34.5 @ BRUCE, rho: x^2 + 3, starting 1000 iterations on C116 10/05/14 22:50:25 v1.34.5 @ BRUCE, rho: x^2 + 2, starting 1000 iterations on C116 10/05/14 22:50:25 v1.34.5 @ BRUCE, rho: x^2 + 1, starting 1000 iterations on C116 10/05/14 22:50:25 v1.34.5 @ BRUCE, pm1: starting B1 = 150K, B2 = gmp-ecm default on C116 10/05/14 22:50:25 v1.34.5 @ BRUCE, current ECM pretesting depth: 0.00 10/05/14 22:50:25 v1.34.5 @ BRUCE, scheduled 30 curves at B1=2000 toward target pretesting depth of 35.69 10/05/14 22:50:26 v1.34.5 @ BRUCE, Finished 30 curves using Lenstra ECM method on C116 input, B1=2K, B2=gmp-ecm default 10/05/14 22:50:26 v1.34.5 @ BRUCE, current ECM pretesting depth: 15.18 10/05/14 22:50:26 v1.34.5 @ BRUCE, scheduled 74 curves at B1=11000 toward target pretesting depth of 35.69 10/05/14 22:50:41 v1.34.5 @ BRUCE, Finished 74 curves using Lenstra ECM method on C116 input, B1=11K, B2=gmp-ecm default 10/05/14 22:50:41 v1.34.5 @ BRUCE, current ECM pretesting depth: 20.24 10/05/14 22:50:41 v1.34.5 @ BRUCE, scheduled 214 curves at B1=50000 toward target pretesting depth of 35.69 10/05/14 22:52:44 v1.34.5 @ BRUCE, Finished 214 curves using Lenstra ECM method on C116 input, B1=50K, B2=gmp-ecm default 10/05/14 22:52:44 v1.34.5 @ BRUCE, pm1: starting B1 = 3750K, B2 = gmp-ecm default on C116 10/05/14 22:52:47 v1.34.5 @ BRUCE, current ECM pretesting depth: 25.33 10/05/14 22:52:47 v1.34.5 @ BRUCE, scheduled 430 curves at B1=250000 toward target pretesting depth of 35.69 10/05/14 23:07:07 v1.34.5 @ BRUCE, Finished 430 curves using Lenstra ECM method on C116 input, B1=250K, B2=gmp-ecm default 10/05/14 23:07:07 v1.34.5 @ BRUCE, pm1: starting B1 = 15M, B2 = gmp-ecm default on C116 10/05/14 23:07:18 v1.34.5 @ BRUCE, current ECM pretesting depth: 30.45 10/05/14 23:07:18 v1.34.5 @ BRUCE, scheduled 904 curves at B1=1000000 toward target pretesting depth of 35.69 10/06/14 01:26:07 v1.34.5 @ BRUCE, Finished 904 curves using Lenstra ECM method on C116 input, B1=1M, B2=gmp-ecm default 10/06/14 01:26:07 v1.34.5 @ BRUCE, current ECM pretesting depth: 35.56 10/06/14 01:26:07 v1.34.5 @ BRUCE, scheduled 66 curves at B1=3000000 toward target pretesting depth of 35.69 10/06/14 01:54:48 v1.34.5 @ BRUCE, Finished 66 curves using Lenstra ECM method on C116 input, B1=3M, B2=gmp-ecm default 10/06/14 01:54:48 v1.34.5 @ BRUCE, final ECM pretested depth: 35.70 10/06/14 01:54:48 v1.34.5 @ BRUCE, scheduler: switching to sieve method 10/06/14 01:54:48 v1.34.5 @ BRUCE, nfs: commencing nfs on c116: 38248148288262939877592328434712626897417157843496786404118652121030605576532119227866057116701426977912061693502551 10/06/14 01:54:48 v1.34.5 @ BRUCE, nfs: commencing poly selection with 1 threads 10/06/14 01:54:48 v1.34.5 @ BRUCE, nfs: setting deadline of 7650 seconds 10/06/14 03:59:15 v1.34.5 @ BRUCE, nfs: completed 44 ranges of size 250 in 7466.9067 seconds 10/06/14 03:59:15 v1.34.5 @ BRUCE, nfs: best poly = # norm 4.575890e-011 alpha -5.879554 e 4.598e-010 rroots 3 10/06/14 03:59:15 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 05:11:38 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 06:25:39 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 07:34:46 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 08:49:54 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 10:00:20 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 11:16:24 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 12:30:38 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 13:43:13 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 15:04:15 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 16:20:10 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 17:31:18 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 18:45:41 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 19:58:42 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 21:10:20 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 22:26:56 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/06/14 23:45:59 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/07/14 00:57:21 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads 10/07/14 02:17:26 v1.34.5 @ BRUCE, nfs: commencing lattice sieving with 1 threads LatSieveTime: 4329 LatSieveTime: 4425 LatSieveTime: 4129 LatSieveTime: 4493 LatSieveTime: 4205 LatSieveTime: 4546 LatSieveTime: 4436 LatSieveTime: 4339 LatSieveTime: 4842 LatSieveTime: 4536 LatSieveTime: 4251 LatSieveTime: 4440 LatSieveTime: 4363 LatSieveTime: 4281 LatSieveTime: 4575 LatSieveTime: 4724 LatSieveTime: 4266 LatSieveTime: 4775 LatSieveTime: 4860 0 12348.187500 |
|
3)
Message boards :
Number crunching :
So how long is your C116 Task?
(Message 722)
Posted 7 Oct 2014 by Bruce Kennedy Post: I have a C116 that has been running for 24 hours now using all 8 cores and is at 99.999% for the last 4 hours or so. I appears the CPU time is stuck also at 03:25:31. Will it ever finish on my i7-4700HQ? If it's not done in the next 12 hours or so I'll cancel it. |
|
4)
Message boards :
Number crunching :
why does it need all 8 cores to run
(Message 508)
Posted 28 Nov 2012 by Bruce Kennedy Post: Actually yafu doesn't need all 8 cores to run..... if you trick it! 1. set all projects to no new work. 2. set ncpus in cc_config to # of cores you want to use for yafu. (5 or more) 3. read cc_config for change to take effect. 4. allow new work for yafu. 5. bump minimum work buffer up by 2 days in preferences. 6. downloaded yafu WUs only need # of cores entered in step 2, not all 8. 7. set ncpus back to 8 and repeat step 3. 8. drop minimum work buffer down by 2 days. 8. allow new work for other desired projects. 9. set yafu to no new work otherwise new WUs will take all 8 cores. 10. if needed, suspend any running tasks for a few seconds to get yafu started. This will keep you crunching yafu for a couple of days and allow GPU and other CPU tasks to run as well. I have not tried setting ncpus to 4 or less. It may allow multiple yafu tasks to run at the same time and defeat the goal. This process takes a few minutes and it would be far better if yafu had a way to select the # of cores in project preferences. Another method is to fire up a virtual machine with the number of cores you want for yafu. |