mfakto update, please
 

Dubslow mentioned I might want to comment on the mfakto-part of the pdf ... sorry I did not take part in that earlier.

And indeed, the "DO NOT SUBMIT “NO FACTOR” RESULTS YET" statement is a bit outdated. Apart from the bug with version 0.08 that may lead to missed factors < 2[SUP]48[/SUP], there's no known reason for not reporting all results.

Regarding the Factor size: There is no lower limit for the factors, so for mfaktc this should just read "Factor size <= 2[SUP]95[/SUP] ". mfakto does not yet have the 95-bit kernel, so for mfakto the limit is "Factor size <= 2[SUP]92[/SUP] ".

As an estimated GIMPS score you can use (maybe I should test that some day):

roughly 60 GHz days/day on HD5770 & 2 CPU cores

This is also a bit misleading: "mfakto works best on large exponents as the sieving (CPU) part stays constant with larger numbers."
mfakto (and mfaktc) are more efficient with larger assignments. This does not mean larger exponents, but "more work" or "longer runtime per class", generally bigger bit ranges. The reason is a certain one-time initialization effort per class - no matter if the class will just test 1 million factor candidates or 1 billion. In the first case, the one-time effort may account for, say, 75% of the sieving effort, in the latter case just 0.3%. Plus there is an average of half a block wasted for each class. If the class consists of only one block, that's 50%, for 1000 blocks it's just 0.05%.

Thanks
 

I'm going to integrate this information asap.

[QUOTE=Brain;277534]I'm going to integrate this information asap.[/QUOTE]
You may want to add about the mini-pirmenet that Chasall has set up to aid the factoring to extra bit depths ahead of the LL 'wave front'.

[QUOTE=Bdot;277484]

As an estimated GIMPS score you can use (maybe I should test that some day):

roughly 60 GHz days/day on HD5770 & 2 CPU cores
[/QUOTE]

I just checked the crunching-power of my HD5770-box. The last 24 hrs returned 96.6 GHz-days, using 3 CPU-cores. So I guess mentioning 90 GHz-days/day with 2 cores should be quite safe.

GPU Computing Guide Update to v 0.06
 

This is a replacement for 0.05a. Please review.

Several minor changes:
[LIST][*]mfakto: All results submittable[*]mfakto: Decreased upper factor size limit[*]GPU to 72 tool[*]ATI driver warning for 11.10[*]ATI: GIMPS score estimate added[*]CUDALucas: Unknown upper limit[*]Call for P-1 and ECM implementations[/LIST][URL="http://www.mersenneforum.org/attachments/pdfs/GIMPS_GPU_Computing_Cheat_Sheet.pdf"]GIMPS GPU Computing Cheat Sheet (pdf)[/URL]

[QUOTE=Brain;277630]P.S.: We still need somebody to implement the following work types on a GPU:
-- P-1 factoring
-- ECM factoring
Code it and enter the GIMPS hall of fame…[/QUOTE]

How about CudaNFS, CudaQS/SIQS/MPQS (at least for init phase)? :smile:
Will it have some effect on the speed(time)? etc.

[QUOTE=LaurV;277666]How about CudaNFS, CudaQS/SIQS/MPQS (at least for init phase)? :smile:
Will it have some effect on the speed(time)? etc.[/QUOTE]Undoubtedly possible, but doubtedly worth the effort for NFS. Assuming, that is, you want the sieving phase to be implemented in CUDA. Polynomial selection is already available in msieve. Filtering is too I/O intensive to make sense to port to CUDA and I don't yet have a good enough feel for the square root phase to make sensible comments.

As a rule, GPUs are good at computation, poor at memory access and lousy at I/O compared with CPUs. The sieving phase is very heavily memory bound ...


Paul

Thanks for the answer, it was more like a curiosity, my understanding of NFS is almost zero at this time.

[QUOTE=Brain;277630]This is a replacement for 0.05a. Please review.

Several minor changes:
[LIST][*]mfakto: All results submittable[*]mfakto: Decreased upper factor size limit[*]GPU to 72 tool[*]ATI driver warning for 11.10[*]ATI: GIMPS score estimate added[*]CUDALucas: Unknown upper limit[*]Call for P-1 and ECM implementations[/LIST][/QUOTE]
garo...
or some other mod...
(and the other FAQ thread as well)

Looking for an old post, found that this PDF is still v.06, while the other FAQ has v.07.

BTW, mfakto 0.10 / 0.10p1 solved the issues with the latest Catalyst drivers. 11.10 to 11.12 are tested well.