Trial factoring with mfakto and gpuowl

[masser]

Originally Posted by SELROC

I have tried to use the special page, every option gives the error no assignments available for gpu.

Try:

Number of assignments: 1000
Preferred work range: TF for first-time LLs
Optional exponent range: 95000000 to 96000000
Work preference: Lowest Bit Levels
Optional Bit Level to factor to: 72

That should work. Keep in mind, GPU72 reserves large swaths of exponents immediately ahead of the P-1/LL (1st time) wavefronts. If you follow the stats on mersenne.ca, you'll get a sense of where most of the TF work is occurring.

P.S. Keeping an eye on www.mersenne.org/primenet/ helps too.

[ET_]

I started using mfakto witn an INTEL HD4400 GPU. Not as speedy as a "real" Nvidia or AMD, but worth at leasat 5 more GHz-days/day.

as I never used mfakto before, I noticed some tuning parameters on the INI file I never encountered on mfaktc for Nvidia:

# Different GPUs may have their best performance with different kernels
# Here, you can give a hint to mfakto on how to optimize the kernels.
#
# Possible values:
# GPUType=AUTO             try to auto-detect, if that does not work: let me know
# GPUType=GCN              Tahiti et al. (HD77xx-HD79xx), also assumed for unknown devices.
# GPUType=VLIW4            Cayman (HD69xx)
# GPUType=VLIW5            most other AMD GPUs (HD4xxx, HD5xxx, HD62xx-HD68xx)
# GPUType=APU              all APUs (C-30 - C-60, E-240 - E-450, A2-3200 - A8-3870K) not sure if the "small" APUs would work better as VLIW5.
# GPUType=CPU              all CPUs (when GPU not found, or forced to CPU)
# GPUType=NVIDIA           reserved for Nvidia-OpenCL. Currently mapped to "CPU" and not yet functional on Nvidia Hardware.
# GPUType=INTEL            reserved for Intel-OpenCL (e.g. HD4000). Not yet functional.
#
# Default: GPUType=AUTO 

GPUType=AUTO

What should I use with my Intel environment, INTEL or AUTO?

And how can I get the best from it? Should I tweak GPUSievePrimes, GPUSieveSize or GPUSieveProcessSize to have the best performances on my INTEL GPU?

Luigi
---

[kriesel]

Originally Posted by ET_

I started using mfakto witn an INTEL HD4400 GPU. Not as speedy as a "real" Nvidia or AMD, but worth at leasat 5 more GHz-days/day.

as I never used mfakto before, I noticed some tuning parameters on the INI file I never encountered on mfaktc for Nvidia:

# Different GPUs may have their best performance with different kernels
# Here, you can give a hint to mfakto on how to optimize the kernels.
#
# Possible values:
# GPUType=AUTO             try to auto-detect, if that does not work: let me know
# GPUType=GCN              Tahiti et al. (HD77xx-HD79xx), also assumed for unknown devices.
# GPUType=VLIW4            Cayman (HD69xx)
# GPUType=VLIW5            most other AMD GPUs (HD4xxx, HD5xxx, HD62xx-HD68xx)
# GPUType=APU              all APUs (C-30 - C-60, E-240 - E-450, A2-3200 - A8-3870K) not sure if the "small" APUs would work better as VLIW5.
# GPUType=CPU              all CPUs (when GPU not found, or forced to CPU)
# GPUType=NVIDIA           reserved for Nvidia-OpenCL. Currently mapped to "CPU" and not yet functional on Nvidia Hardware.
# GPUType=INTEL            reserved for Intel-OpenCL (e.g. HD4000). Not yet functional.
#
# Default: GPUType=AUTO 

GPUType=AUTO

What should I use with my Intel environment, INTEL or AUTO?

And how can I get the best from it? Should I tweak GPUSievePrimes, GPUSieveSize or GPUSieveProcessSize to have the best performances on my INTEL GPU?

Luigi
---

With all due respect, this thread is probably not the best suited. Your questions might get more response if placed in the mfakto thread http://www.mersenneforum.org/showthread.php?t=15646
That said, I like your let-no-GIMPS-capable-hardware-go-idle approach.

[science_man_88]

Originally Posted by ET_

I started using mfakto witn an INTEL HD4400 GPU. Not as speedy as a "real" Nvidia or AMD, but worth at leasat 5 more GHz-days/day.

as I never used mfakto before, I noticed some tuning parameters on the INI file I never encountered on mfaktc for Nvidia:

# Different GPUs may have their best performance with different kernels
# Here, you can give a hint to mfakto on how to optimize the kernels.
#
# Possible values:
# GPUType=AUTO             try to auto-detect, if that does not work: let me know
# GPUType=GCN              Tahiti et al. (HD77xx-HD79xx), also assumed for unknown devices.
# GPUType=VLIW4            Cayman (HD69xx)
# GPUType=VLIW5            most other AMD GPUs (HD4xxx, HD5xxx, HD62xx-HD68xx)
# GPUType=APU              all APUs (C-30 - C-60, E-240 - E-450, A2-3200 - A8-3870K) not sure if the "small" APUs would work better as VLIW5.
# GPUType=CPU              all CPUs (when GPU not found, or forced to CPU)
# GPUType=NVIDIA           reserved for Nvidia-OpenCL. Currently mapped to "CPU" and not yet functional on Nvidia Hardware.
# GPUType=INTEL            reserved for Intel-OpenCL (e.g. HD4000). Not yet functional.
#
# Default: GPUType=AUTO 

GPUType=AUTO

What should I use with my Intel environment, INTEL or AUTO?

And how can I get the best from it? Should I tweak GPUSievePrimes, GPUSieveSize or GPUSieveProcessSize to have the best performances on my INTEL GPU?

Luigi
---

Just reading the lines( not having ever used the software) I'd say AUTO; as INTEL says not yet functional in it's comment.

Originally Posted by science_man_88

Just reading the lines( not having ever used the software) I'd say AUTO; as INTEL says not yet functional in it's comment.

And if you select AUTO it will end up with GCN for an unknown device, INTEL being not functional.