Quick Question about assignments

[Dubslow]

I dunno about tables, but I can give a quick overview of each assignment. (For the record, any assignment will put full, 100% load on the cpu, but I'm assuming that's not what you meant.)

Trial factoring varies heavily depending on what bit levels you're doing it at. Low-limit assignments are very, very short, i.e. a few minutes, maybe 15 on an average processor. "Normal" trial factoring again depends on the factoring depth (each bit takes twice as long as the previous one) but typical assignments take from a quarter of a day to one or two days, depending on the assignment and cpu speed.

P-1 factoring is another way to find factors, and again, varies with circumstances. A typical assignment will take one or two days, or for a large assignment maybe three. The second stage will also use 500MB - 1GB of memory (RAM) or more if you let it.

LL testing is very, very long. Current LL assignments take me a month, and I have Intel's fastest processor. On average they can be anywhere from a month to three or four or more, depending heavily on cpu speed.

All these time estimates assume you run P95 24 hours per day.

As for why it's not queuing 5 days of work, my guess (only a guess) would be that because each assignment is 15 minutes long, that even 1 day of work is ~100 assignments, and it's not getting more than some preset maximum. Guys, any other ideas?

[Wizzard]

Ok, I see, that TF to low limits is the fastest work. Also it seems that different CPUs get different TF limits in normal TF assignments according to that CPU speed.

LL testing, double checking and P-1 testing is very slow.

What about ECM of small Mersenne numbers and Fermat numbers?

About that queuing 5 DOW, it seems that the number of assignments per CPU is limited to 15.

[ET_]

Originally Posted by Wizzard

Ok, I see, that TF to low limits is the fastest work. Also it seems that different CPUs get different TF limits in normal TF assignments according to that CPU speed.

LL testing, double checking and P-1 testing is very slow.

What about ECM of small Mersenne numbers and Fermat numbers?

About that queuing 5 DOW, it seems that the number of assignments per CPU is limited to 15.

ECM on small exponents may be somewhat between TF-low and TF.
ECM on Fermat numbers is between LL-D and LL.

Luigi

[Mr. P-1]

Originally Posted by Wizzard

About that queuing 5 DOW, it seems that the number of assignments per CPU is limited to 15.

You can change this limit by putting

MaxExponents=100

or whatever number you choose, into prime.txt. See undoc.txt for details.

[Wizzard]

^^ Thank you very much, gyus

[Mr. P-1]

Originally Posted by Dubslow

P-1 factoring is another way to find factors, and again, varies with circumstances. A typical assignment will take one or two days, or for a large assignment maybe three. The second stage will also use 500MB - 1GB of memory (RAM) or more if you let it.

P-1 factoring is the worktype the project most needs currently. The minimum memory requirement to be given this type of work is 300MB and you can do a perfectly respectable job with that minimum. More is better, and the client will happily gobble up as much ram as you can throw at it. The returns from allowing more memory diminish rapidly and are really quite marginal after 1GB or so.

Trial factorisation is the least needed worktype, as far as CPUs are concern. GPUs leave CPUs in the dust, and have basically made them obsolete at this task.

[Wizzard]

Okay, I will consider running P-1 factoring.

You said, that GPUs can run Prime95 too or what? It means, I may run Prime95 at my graphics card? :)

[Mr. P-1]

Originally Posted by Wizzard

Okay, I will consider running P-1 factoring.

You said, that GPUs can run Prime95 too or what? It means, I may run Prime95 at my graphics card? :)

GPUS cannot run Prime95. There are, however, other programs which use some GPUs to do blisteringly fast TF and somewhat fast LL testing. These programs are not as mature as Prime95, and need more user intervention to keep things running.

Check out the GPU computing forum for more information.

[Wizzard]

I set the memory usage to 300 MB and work type to P-1 factoring. First CPU core assigned P-1 testing, second core ECM testing. I tried to increase memory to 600 MB, but the same result, and all the memory was used to first core P-1 and that work was restarted.

Is it possible to run P-1 on both CPU cores?

[kladner]

Originally Posted by Wizzard

I set the memory usage to 300 MB and work type to P-1 factoring. First CPU core assigned P-1 testing, second core ECM testing. I tried to increase memory to 600 MB, but the same result, and all the memory was used to first core P-1 and that work was restarted.

Is it possible to run P-1 on both CPU cores?

You can set the assignments individually by core. Go to the Test menu>Worker Windows. If you look at individual worker numbers in the first drop-down, you can then set work type and core affinity for each one.

[Wizzard]

Originally Posted by kladner

You can set the assignments individually by core. Go to the Test menu>Worker Windows. If you look at individual worker numbers in the first drop-down, you can then set work type and core affinity for each one.

Yes, but the problem is, that I have set the options for All workers to P-1 factoring and Run on any CPU.