Hi,

[QUOTE=frmky;310901]My poor S1070. :cry:[/QUOTE]

no, the situation is not that bad. The current development (0.20) does not run very well (slow performance) on CC 1.x GPUs [B]iff[/B] sieving is done on [B]G[/B]PU.
There will be new kernels in mfaktc 0.20 and depending on the factor size (above 2[SUP]76[/SUP]) you'll notice a performance improvement even on CC 1.x GPUs.
So the questions/suggestions are more about how much effort should be spent on CC 1.x GPUs? Currently I don't plan to drop support on CC 1.x GPUs but I don't spent much time on optimizations for CC 1.x, got the idea?
I was thinking about disabling GPU sieving on CC 1.x GPUs (just because it runs slow), this will save some time during testing.

Oliver
P.S. thank you George and rcv for GPU sieving, thank you George for the new kernels :smile:

[QUOTE=TheJudger;311146]
P.S. thank you George and rcv for GPU sieving, thank you George for the new kernels :smile:[/QUOTE]

Thank you Oliver for not dropping cc 1.3 :bow:

Luigi

Resume from chekpoint file with mfaktc 0.19
 

[COLOR=black][FONT=Verdana][I]I have a question, which maybe not is a big issue, but anyway:[/I][/FONT][/COLOR]
[COLOR=black][FONT=Verdana][I]A HDD was smoked on one of my systems, but happily I was able to rescue the intermediary results from mfaktc 0.19 from the old hard drive. I was happy because I am doing some work for Operation Billion Digits high up between ^85 and ^86.[/I][/FONT][/COLOR]
[COLOR=black][FONT=Verdana][I]Now I have installed a new disk and Windows fresh from the beginning on that disk.[/I][/FONT][/COLOR]
[COLOR=black][FONT=Verdana][I]When I tried to resume from last checkpoint-file mfaktc 0.19 refuses me to resume and insists that I should begin trial factoring from the beginning. This would mean that I would loose a couple of weeks of work, so I wonder if there is a way to resume?[/I][/FONT][/COLOR]

[B]Sorry, I just looked at the content of the checkpoint files and there are only blank spaces, no real content. So the old Hard disk was in a worse state then I thought! Nothing to do then, sorry for taking your time.[/B]

My Pentium D 940 CPU can't feed my GTX 460 fully. I can get 24 Ghz-Days/day running 24/7 instead of however many it should get (~120).

c10ck3r: I guess the poor performance is related to the relative small L1 cache size. You'll like mfaktc 0.20 once it is finished.

Oliver

Btw: CPU Launch date Q1'06 vs. Q3'10 GTX 460, this is four and a half year difference...

It is technically my mothers desktop, with my GPU and PSU... This summer I hope to add a desktop of my own...

I had a similar problem with a Core2Quad and a 480, could not max out the GPU even with all 4 cores running mfaktc. A single core of my 2500 outproduced the entire quad on the 480.

Could we please have Prime95-style timestamps accompany the results? That would be quite useful!

Edit: Never mind, I found out that I can configure it in mfaktc.ini.

I would also like to see the option to do sieve on the GPU only like mmff. How hard is that?

[QUOTE=flashjh;316901]I would also like to see the option to do sieve on the GPU only like mmff. How hard is that?[/QUOTE][url=http://www.mersenneforum.org/showpost.php?p=311146&postcount=1904]Oliver's post[/url] from 2 months ago seems to indicate it's planned for inclusion in mfaktc v0.20, and presumably working (at least in alpha form) at that time.

[QUOTE=James Heinrich;316905][URL="http://www.mersenneforum.org/showpost.php?p=311146&postcount=1904"]Oliver's post[/URL] from 2 months ago seems to indicate it's planned for inclusion in mfaktc v0.20, and presumably working (at least in alpha form) at that time.[/QUOTE]
That's right, I forgot. I know it won't be as fast, but it will be nice to use the CPU for something else.