Sorry, for being vague and not replying sooner.
Yes, I did indeed mean that YAFU was spending too much time in polysearch in relation to the whole factorization. This is especially prevalent for smaller composites.
But this could also be caused by me using a 16core/32 threads machine (Ubuntu).
For instance with RSA120
Code:
02/03/19 14:41:16 v1.35beta @ SupermicroXeonE52650, nfs: commencing nfs on c120: 227010481295437363334259960947493668895875336466084780038173258247009162675779735389791151574049166747880487470296548479
02/03/19 14:41:16 v1.35beta @ SupermicroXeonE52650, nfs: commencing poly selection with 32 threads
02/03/19 14:41:16 v1.35beta @ SupermicroXeonE52650, nfs: setting deadline of 13500 seconds
02/03/19 14:41:16 v1.35beta @ SupermicroXeonE52650, nfs: expecting degree 5 poly E from 2.87e10 to > 3.30e10
02/03/19 14:41:16 v1.35beta @ SupermicroXeonE52650, nfs: searching for min quality poly E > 2.87e10
02/03/19 15:27:25 v1.35beta @ SupermicroXeonE52650, nfs: completed 80 ranges of size 50 in 2768.6909 seconds
02/03/19 15:27:25 v1.35beta @ SupermicroXeonE52650, nfs: best poly = # norm 2.225654e11 alpha 6.557326 e 3.097e10 rroots 5
02/03/19 15:27:25 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:29:12 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:30:59 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:32:46 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:34:27 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:36:21 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:38:04 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:39:51 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:41:37 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:43:26 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:45:18 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:47:07 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:48:56 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:50:45 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:52:30 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:54:25 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:56:17 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:58:09 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 15:59:55 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:01:41 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:03:30 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:05:24 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:07:17 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:09:10 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:11:04 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:12:58 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:14:45 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:16:35 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:18:19 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:20:12 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:22:05 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:23:55 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:25:48 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:27:39 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:29:28 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:31:23 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:33:22 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:35:10 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:37:11 v1.35beta @ SupermicroXeonE52650, nfs: commencing msieve filtering
02/03/19 16:40:33 v1.35beta @ SupermicroXeonE52650, nfs: raising min_rels by 5.00 percent to 10631389
02/03/19 16:40:33 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:42:24 v1.35beta @ SupermicroXeonE52650, nfs: commencing lattice sieving with 32 threads
02/03/19 16:44:20 v1.35beta @ SupermicroXeonE52650, nfs: commencing msieve filtering
02/03/19 16:48:21 v1.35beta @ SupermicroXeonE52650, nfs: commencing msieve linear algebra
02/03/19 16:57:21 v1.35beta @ SupermicroXeonE52650, nfs: commencing msieve sqrt
02/03/19 16:59:22 v1.35beta @ SupermicroXeonE52650, prp60 = 693342667110830181197325401899700641361965863127336680673013
02/03/19 16:59:22 v1.35beta @ SupermicroXeonE52650, prp60 = 327414555693498015751146303749141488063642403240171463406883
02/03/19 16:59:22 v1.35beta @ SupermicroXeonE52650, NFS elapsed time = 8286.1046 seconds.
It was spending 2769 seconds in polysearch.
2769/8286 = 33.4% of the time. It should've been about 1015% of the time.
Quote:
Originally Posted by bsquared
I should maybe also (re)mention that if you don't want to search for a fixed time, you can use the psearch option with either min,avg, or good as a qualifier. yafu will stop when it finds a {min,avg,good} poly for the input number.
min,avg,good are chosen based on Batalov's heuristic.
psearch min > uses a multiplier of 1 to that fit
psearch avg > uses a multipler of 1.036
psearch good > uses a multiplier of 1.072

I wasn't aware of that option, I'll try that and see if it helps!