[QUOTE=James Heinrich;472780]
Previously-missed TF factors have been found in the past by random re-checks.[/QUOTE]

Also P-1 factoring may turn up a missed trial factor.

[QUOTE=James Heinrich;472780]In my opinion the only way to minimize the problem is to not give credit for TF that doesn't find factors. Just credit finding factors only, make no public record of how much no-factor TF any user does, and there's no incentive to submit false results.[/QUOTE]

I'd be in favour of this change with regards to credit given. I think having a public record of work done is useful though because it has proven useful in the past to redo TF work done by a dodgy machine (I found many factors).

If people want lots of results, they could easily do the high exponents and find factors more quickly, so hiding no-factor work probably wouldn't help much.

[QUOTE=Mark Rose;472786]If people want lots of results, they could easily do the high exponents and find factors more quickly[/QUOTE]Such as my [URL="http://www.mersenne.ca/tf1G.php"]TF>1000M subproject[/URL] where you can find still find 1-2 factors per minute in the current ranges. :smile:

Not getting credit will not prevent malicious users from messing your databases up. This is my fear.


Some questions:

1) Can I pause trial factoring? Ctrl+C? There is "a bit" of video lag.
2) How do I skip TF on P95 after my GPU will complete all the remaining TF tests? I thought PrimeNet would have aborted my TF by CPU (currently paused).
2) How can I run TF for >1000M exponents? Is manual assignment enough?

1) You can pause TF at any time. Easiest way (on Windows at least) is to hit the Pause/Break key (ie the one above PageUp on your keyboard) and that will actually pause it, any other key will resume it. Ctrl-C will terminate close mfatkc (after it finishes the current class) and it will write a checkpoint so it can resume from there next time you start it (assuming Checkpoints=1 in mfaktc.ini)

2) If you have been (somehow?) assigned an assignment that is insufficiently TF'd and Prime95 wants to do more TF on it (this would surprise me greatly -- what exponent is it?) but you are doing the extra TF on your GPU, you can close Prime95, edit the Prime95 worktodo.txt and change the current TF limit to the new limit that you have TF'd on your GPU, then restart Prime95. But I'm curious as to what assignment you have been assigned that would make Prime95 do TF?

3) Go to [url]http://www.mersenne.ca/tf1G.php[/url] and click "Get Assignments" at the top. Read all the tips in the box on the right. You can do manual assignments if you choose, but I would highly recommend the provided "simple Windows batch file for automated work fetch/submit" that's posted there because there's a huge amount of churn, assignments only take a very few seconds so you can easily go through tens of thousands of assignments per day.

1) I'm on Linux. So i will try Ctrl+C. Checkpoints=1 in my mfaktc.ini.

2) A world record LL test: [URL]https://www.mersenne.org/report_exponent/?exp_lo=333467413&full=1[/URL]

3) Maybe I can write a bash script. However, I don't think to run 24/7 for now.

1) Pause/Break may work on linux as well, I don't know, but it's worth a quick test.
3) The Windows batch file should be pretty trivial to translate into a bash script. It basically just runs mfaktc in a loop and when it runs out of work it uses curl and wget to send results and retrieve new assignments. If you do translate it please send me a copy so I can make it available for others.

On a side note, besides it being my pet project, I find running small TF assignments works very well with my GPU, zero impact in normal use; I only pause it for some games, whereas TF in the normal ~80M range to higher bit depths causes noticeable GUI lag, no matter what mfakto.ini settings I set.

[QUOTE=James Heinrich;472855]1) Pause/Break may work on linux as well, I don't know, but it's worth a quick test.
3) The Windows batch file should be pretty trivial to translate into a bash script. It basically just runs mfaktc in a loop and when it runs out of work it uses curl and wget to send results and retrieve new assignments. If you do translate it please send me a copy so I can make it available for others.

On a side note, besides it being my pet project, I find running small TF assignments works very well with my GPU, zero impact in normal use; I only pause it for some games, whereas TF in the normal ~80M range to higher bit depths causes noticeable GUI lag, no matter what mfakto.ini settings I set.[/QUOTE]

Hmm, on most of my laptop keyboards, not only is the pg up key in the top row of keys, but there is no key present with label containing pause or break. I use one such laptop to manage many GPU-equipped systems via remote desktop.

[QUOTE=kriesel;472859]Hmm, on most of my laptop keyboards, not only is the pg up key in the top row of keys, but there is no key present with label containing pause or break. I use one such laptop to manage many GPU-equipped systems via remote desktop.[/QUOTE][url]https://en.wikipedia.org/wiki/Break_key#Keyboards_without_Break_key[/url]

Mfaktc throughput variables
 

Hi,

Finally got around to investigating Mfaktc consistently indicating 98% GPU usage in GPU-Z., rather than the 100% that CUDAPm1 and CUDALucas typically produce There are slight gains in total throughput to be had by running multiple instances. There are confounding factors, including:

Definitely:
Exponent being run (substantial effect)
Factoring depth being run (minor effect)
Overhead of running the screen display with the same GPU (varying effect)

Probably:
GPU clock throttling due to thermal limits

Potentially, at high exponent or instance count:
memory constraints (although mfaktc doesn't use much memory per instance at current wavefront exponents)

Load sharing for multiple instances appears to be not quite equal; they have slightly differing throughputs.

An operational advantage of running multiple instances is being able to stop one, add work, look at results, change ini file settings, etc, without noticeable loss of throughput; the others will essentially saturate the GPU while one instance is out of action temporarily. If one instance runs out of work the other running instances run a bit faster than if it hadn't, limiting lost total throughput.

Attached results are for a GTX480.

[QUOTE=Luis;472854]1) I'm on Linux. So i will try Ctrl+C. Checkpoints=1 in my mfaktc.ini.

2) A world record LL test: [URL]https://www.mersenne.org/report_exponent/?exp_lo=333467413&full=1[/URL]

3) Maybe I can write a bash script. However, I don't think to run 24/7 for now.[/QUOTE]

I wrote scripts that stop mfaktc on my primary GPU when I unlock my screensaver and resume on lock.