[QUOTE=Xyzzy;324971]It would be convenient to be able to click a button and pause activity, and maybe have the activity resume automatically in an hour. Or maybe have mfaktc run at a lower priority or do a "PauseWhileRunning" deal.

Is this something that could be easily coded?
[/QUOTE]
If you open the DOS window where a program is running and [COLOR=lemonchiffon][SPOILER][COLOR=lemonchiffon]select[/COLOR][/SPOILER][/COLOR] part of the text, the program will suspend (not immediately, but after the current class will be done); it is a side-effect of DOS, I guess. I instructed my son to do that before he plays his games. When he is done - open the window again and right-click in it once, which will release the selection.

Another way to do is with [URL="http://en.wikipedia.org/wiki/Process_Explorer"]Process Explorer[/URL].

[QUOTE=Batalov;324993]If you open the DOS window where a program is running and [COLOR=lemonchiffon][SPOILER][COLOR=lemonchiffon]select[/COLOR][/SPOILER][/COLOR] part of the text, the program will suspend (not immediately, but after the current class will be done); it is a side-effect of DOS, I guess. I instructed my son to do that before he plays his games. When he is done - open the window again and right-click in it once, which will release the selection.

Another way to do is with [URL="http://en.wikipedia.org/wiki/Process_Explorer"]Process Explorer[/URL].[/QUOTE]

What about those of us who use various forms of GNU/Linux (or BSD)? :judge:


[COLOR=green]SB: That's too-oo easy! [B]killall -STOP mfaktc[/B] and later [B]killall -CONT mfaktc [/B][/COLOR]
[COLOR=green]Linux presents no problem! It is Windows that is a problem![/COLOR]

[QUOTE=kracker;324986]I would be curious as to how much a 660 Ti spits out too :smile:[/QUOTE][url=http://mersenne.ca/mfaktc.php]223.6 GHz-days/day[/url] (based on estimates from a single CC 3.0 benchmark).

[QUOTE=Batalov;324993]If you open the DOS window where a program is running and [COLOR=lemonchiffon][SPOILER][COLOR=lemonchiffon]select[/COLOR][/SPOILER][/COLOR] part of the text, the program will suspend ... open the window again and right-click in it once, which will release the selection.[/QUOTE]Much easier: use the handy "Pause" key on your keyboard. Pauses immediately, and resumes on almost any key press (other than Pause and modifier keys like Shift/Alt/Ctrl). Not sure if same applies to Linux, but does work outside DOS and Windows (such as during POST).

Well, it doesn't pause [I]immediately[/I], -- only just as well as selection. The signal is not being transferred to the GPU which will always finish the last class before snoozing (unless you'd kill it).

Interestingly, putty.exe sends "Pause"-press to the ssh'd host as Ctrl-Z. (but of course it won't unpause for you later with any-key) That's convenient if you use putty ...even though Ctrl-Z also works always.

Plain Linux surely disregards this key (and it's evil brother "Ctrl-pause") (but as any key or key combination it is probably configurable).

[QUOTE=Xyzzy;324971]It would be convenient to be able to click a button and pause activity, and maybe have the activity resume automatically in an hour. Or maybe have mfaktc run at a lower priority or do a "PauseWhileRunning" deal.

Is this something that could be easily coded?

We have no problem stopping the program but we frequently forget to restart it.

We are currently running on a GT 430 but we have a GTX 660Ti to install tomorrow.[/QUOTE]
Ahhhh... so long I waited for this, but I expected it to come from Dubslow, to be able to tell him back: "Use windows!" :yucky:
There is a "pause/break" key, which (temporarily) stops mfaktc until you press the "space" key.

[edit: grrr did not see there is a new page]

[QUOTE=Dubslow;324994]What about those of us who use various forms of GNU/Linux (or BSD)? :judge:


[COLOR=green]SB: That's too-oo easy! [B]killall -STOP mfaktc[/B] and later [B]killall -CONT mfaktc [/B][/COLOR]
[COLOR=green]Linux presents no problem! It is Windows that is a problem![/COLOR][/QUOTE]

Control-S in the mfaktc window works under Windows, so you'd think it would work under Linux too. Control-Q (or any other key in Win) to continue.

I always assume
control= DanceMyPuppet

My display does not lag on GTX 560 Ti generally but only in the game I play. So I start the game with a batch file:

[CODE]
pssuspend mfaktc-win-32
pssuspend -r mfaktc-win-64
xvm-stat.exe
pssuspend -r mfaktc-win-32
pssuspend mfaktc-win-64
[/CODE]

So when I play the game I run CPU sieving copy, otherwise GPU.

[QUOTE=Dubslow;324994]
[COLOR=green]SB: That's too-oo easy! [B]killall -STOP mfaktc[/B] and later [B]killall -CONT mfaktc [/B][/COLOR]
[COLOR=green]Linux presents no problem! It is Windows that is a problem![/COLOR][/QUOTE]

Well duh. :smile: The problem of course is remembering to type `fg` everytime I leave the computer, though as above, I just leave it on now with a much-crippled sieve size.

For a single process I prefer ^Z/fg, though for pausing a bunch of lasieve processes I have two aliases, one each for -STOP and -CONT inside a "for p in `pidof lasieve`; do killall <mode> $p; done" loop. Quite handy things, aliases. :wink:

[QUOTE][url=http://mersenne.ca/mfaktc.php]223.6 GHz-days/day[/url] (based on estimates from a single CC 3.0 benchmark).[/QUOTE]We just finished installing the GTX 660Ti so we ran a benchmark. (This is with the 32-bit executable on 64-bit Windows 7, with all of the parameters set to default.)

[CODE]no factor for M61160719 from 2^70 to 2^71 [mfaktc 0.20 barrett76_mul32_gs]
tf(): total time spent: 22m 15.685s[/CODE]
The lag with the default settings with the GT 430 was 3-4 seconds. Now the lag is maybe half a second at the worst. We still will probably dial back the "GPUSieveSize" setting a bit.

Our next goal is to get the GT 430 installed with the GTX 460Ti and use the GT 430 as a dedicated GPU factoring card.