mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   GPU Computing (https://www.mersenneforum.org/forumdisplay.php?f=92)
-   -   mfaktc: a CUDA program for Mersenne prefactoring (https://www.mersenneforum.org/showthread.php?t=12827)

TheJudger 2012-12-25 23:38

mfaktc 0.20 decission
 
Hi,

please help me making another decission! :smile:
As you may allready know: mfaktc 0.20 will allow sieving done on GPU (for GPUs with CC 2.0 or newer). How should we handle this?[LIST=1][*]disabled by default, enable with commandline switch "[I]-gs[/I]"[*]disabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]enabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]other[/LIST]My vote is #3.
Option #1 is how George has implemented it when he has written the GPU sieve code for mfaktc, options #2/#3 are in sync with mfakt[B][COLOR="Red"]o[/COLOR][/B].

Oliver

Bdot 2012-12-25 23:48

[QUOTE=TheJudger;322618]Hi,

please help me makeing another decission! :smile:
As you may allready know: mfaktc 0.20 will allow sieving done on GPU (for GPUs with CC 2.0 or newer). How should we handle this?[LIST=1][*]disabled by default, enable with commandline switch "[I]-gs[/I]"[*]disabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]enabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]other[/LIST]My vote is #3.
Option #1 is how George has implemented it when he has written the GPU sieve code for mfaktc, options #2/#3 are in sync with mfakt[B][COLOR="Red"]o[/COLOR][/B].

Oliver[/QUOTE]
mfakto does not have a working GPU sieve yet, I just prepared the variable. I will adjust mfakto to mfaktc once I get these kernels to work. Anyway, I'd prefer #3 as well ...

kracker 2012-12-26 00:10

[QUOTE=TheJudger;322618]Hi,

please help me makeing another decission! :smile:
As you may allready know: mfaktc 0.20 will allow sieving done on GPU (for GPUs with CC 2.0 or newer). How should we handle this?[LIST=1][*]disabled by default, enable with commandline switch "[I]-gs[/I]"[*]disabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]enabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]other[/LIST]My vote is #3.
Option #1 is how George has implemented it when he has written the GPU sieve code for mfaktc, options #2/#3 are in sync with mfakt[B][COLOR=Red]o[/COLOR][/B].

Oliver[/QUOTE]

#3 as well.

swl551 2012-12-26 00:12

[QUOTE=TheJudger;322618]Hi,

please help me makeing another decission! :smile:

As you may allready know: mfaktc 0.20 will allow sieving done on GPU (for GPUs with CC 2.0 or newer). How should we handle this?[LIST=1][*]disabled by default, enable with commandline switch "[I]-gs[/I]"[*]disabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]enabled by default, controlled by variable "[I]SieveOnGPU[/I]" in mfaktc.ini[*]other[/LIST]My vote is #3.
Option #1 is how George has implemented it when he has written the GPU sieve code for mfaktc, options #2/#3 are in sync with mfakt[B][COLOR=red]o[/COLOR][/B].

Oliver[/QUOTE]


#3 as well.

VictordeHolland 2012-12-26 00:49

My vote is also on #3
I see a pattern emerging :razz:.

Chuck 2012-12-26 01:11

I like #3.

Chuck

James Heinrich 2012-12-26 02:54

#3, as with everyone else. Specifically, always use GPU sieving when possible (CC 2.0+, >2[sup]64[/sup]) unless explicitly disabled with "SieveOnGPU=0" in mfaktc.ini

axn 2012-12-26 03:22

[QUOTE=TheJudger;322618]
4. other
[/QUOTE]
Intelligent/Smart option -- Do a selftest and pick the one with highest thruput. Can be overridden by <whatever> mechanism.

LaurV 2012-12-26 04:42

[QUOTE=axn;322637]Intelligent/Smart option -- Do a selftest and pick the one with highest thruput. Can be overridden by <whatever> mechanism.[/QUOTE]
Too complicate, not necessarily useful... CPU status can change later (like from busy to free, from free to busy, from partial busy to full busy, etc). leading the "selftest" futile and having various influence on the OTHER tasks/workers using the CPU. The most people prefer to have the CPU free to do other things (P-1??). I'd go with number #3 too.

kladner 2012-12-26 05:28

I agree on the #3 choice. I am eagerly looking forward to experimenting with the new version. I also look forward to having multiple CPU cores to use for other things without impinging on mfaktc performance. Those 'other things' would likely include P-1, but it would be cool to try multi-thread LL in P95. While I know that GPUs can generally do DC or TC faster, there are the times that only a P95 result will do.

flashjh 2012-12-26 05:41

[QUOTE=James Heinrich;322635]#3, as with everyone else. Specifically, always use GPU sieving when possible (CC 2.0+, >2[sup]64[/sup]) unless explicitly disabled with "SieveOnGPU=0" in mfaktc.ini[/QUOTE]
+1


All times are UTC. The time now is 23:16.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.