GPU Trial Factoring FAQ

[Bdot]

Originally Posted by LaurV

Indeed. That is only valid for mfakto, but hopefully not for long either, work is being done (by Bdot and co., if I not mistaken) to add OpenCL GPU sieving too.

I finally released mfakto 0.13 which features GPU sieving similar to mfaktc 0.20. It can be found at http://mersenneforum.org/mfakto/.

Maybe someone could update the thread's entry post (download URL & GPU sieving) and the GPU cheat sheet (also, download URL and GPU sieving)?

[kracker]

Originally Posted by Bdot

I finally released mfakto 0.13 which features GPU sieving similar to mfaktc 0.20. It can be found at http://mersenneforum.org/mfakto/.

Maybe someone could update the thread's entry post (download URL & GPU sieving) and the GPU cheat sheet (also, download URL and GPU sieving)?

I know I asked this before but still, I'm not sure on "GIMPS score estim.", as my low end HD 7770(~$120) does around 175 GHz on DC range, 150 in LL range.

[roemer2201]

Q: Is it possible to change the working directory of mfaktc?

If not, is this the right place for the feature request?

[kladner]

Originally Posted by roemer2201

Q: Is it possible to change the working directory of mfaktc?

If not, is this the right place for the feature request?

From mfaktc.ini, about 1/3 from the top-

# WorkFile: the name of the file which contains the factoring assignments.
# e.g.
# worktodo.ini (Prime95 v24 and earlier)
# worktodo.txt (Prime95 v25 and newer)
#
# Default: WorkFile=worktodo.txt

WorkFile=worktodo.txt

Besides this, you can put mfaktc just about anywhere so long as your batch files, if any, have the right path in them. "Program Files (x86)" in Win 7 is not a good place.

[roemer2201]

The Worktodo-File is just one part, can I change the place for the checkpoint-files and result files, too? If I install mfaktc into a usual installation directory like /usr/local/bin, users wont have write-permission for the ckp-files. Thats the reason why I was asking for a whole working-directory. Or does mfaktc store ckp-files and the results along with the worktodo.txt?

[kladner]

Originally Posted by roemer2201

The Worktodo-File is just one part, can I change the place for the checkpoint-files and result files, too? If I install mfaktc into a usual installation directory like /usr/local/bin, users wont have write-permission for the ckp-files. Thats the reason why I was asking for a whole working-directory. Or does mfaktc store ckp-files and the results along with the worktodo.txt?

Sorry. I was speaking from presumption of Windows. Worktodo, results, and *.ckp files all live in the program directory in Windows. The reason I said "Program Files (x86)" should be avoided is similar to the /usr/local/bin you reference. There are problems with write permissions.

I hope one of the Linux-savvy people will pick this up and give you better answers. Linux or not, I'm not sure if other .ini lines for file locations are possible.

[TheJudger]

mfaktc.ini, checkpoint files, results.txt and worktodo.txt within the same directory or in different directories? For the first case it is really simple (Windows and Linux):

1. put mfaktc.exe into some directory (e.g "C:\programm files\" or "/usr/local/bin/")
2. create your working directory
3. put your worktodo.txt and mfaktc.ini into the working directory
4. start <some directory>/mfaktc.exe in this directory

not even needed to modify mfaktc.ini

Oliver

[firejuggler]

Don't forget the dll

[roemer2201]

Originally Posted by TheJudger

mfaktc.ini, checkpoint files, results.txt and worktodo.txt within the same directory or in different directories? For the first case it is really simple (Windows and Linux):

1. put mfaktc.exe into some directory (e.g "C:\programm files\" or "/usr/local/bin/")
2. create your working directory
3. put your worktodo.txt and mfaktc.ini into the working directory
4. start <some directory>/mfaktc.exe in this directory

not even needed to modify mfaktc.ini

Oliver

So mfaktc allways uses the "pwd" as a workingdirectory? To this i can not agree. I'll attach my mfaktc startskript. There you can see that my pwd is $HOME and I launch the program with ~/bin/mfaktc-0.20/mfaktc.exe. According to your description mfaktc should look for the worktodo.ini directly in my $HOME, right? But what it actually does is that it reads/writes all related files to ~/bin/mfaktc-0.20.

[TheJudger]

Originally Posted by roemer2201

So mfaktc allways uses the "pwd" as a workingdirectory? To this i can not agree. I'll attach my mfaktc startskript. There you can see that my pwd is $HOME and I launch the program with ~/bin/mfaktc-0.20/mfaktc.exe. According to your description mfaktc should look for the worktodo.ini directly in my $HOME, right? But what it actually does is that it reads/writes all related files to ~/bin/mfaktc-0.20.

It should use cwd for all files read an written:

somehost:/tmp # ls -la foo/ bar/
bar/:
total 140
drwxr-xr-x 2 root root   4096 Jun 27 23:29 .
drwxrwxrwt 9 root root 114688 Jun 27 23:26 ..
-rw-r--r-- 1 root root     40 Jun 27 23:29 M66362159.ckp
-rw-r--r-- 1 root root   8730 Jun 27 23:27 mfaktc.ini
-rw-r--r-- 1 root root     28 Jun 27 23:29 worktodo.txt

foo/:
total 764
drwxr-xr-x 2 root root   4096 Jun 27 23:27 .
drwxrwxrwt 9 root root 114688 Jun 27 23:26 ..
-rwxr-xr-x 1 root root 652622 Jun 27 23:27 mfaktc.exe

somehost:/tmp # cd bar/
somehost:/tmp/bar # ../foo/mfaktc.exe
mfaktc v0.20 (64bit built)
[...]
got assignment: exp=66362159 bit_min=64 bit_max=65 (0.06 GHz-days)
Starting trial factoring M66362159 from 2^64 to 2^65 (0.06 GHz-days)
 k_min = 138985409640
 k_max = 277970824814
Using GPU kernel "barrett76_mul32_gs"

found a valid checkpoint file!
  last finished class was: 105
  found 0 factor(s) already
[...]

Please check

ls -la /proc/<PID of mfaktc>/cwd

Oliver

[roemer2201]

Originally Posted by TheJudger

[/CODE]Please check

ls -la /proc/<PID of mfaktc>/cwd

Oliver

Thanks for that tip. You are right, my cwd is the folder with the binary of mfaktc. So it should be easy to customize the script to my needs.