View Single Post
2020-10-18, 15:00   #3359
kriesel

"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

113538 Posts

Quote:
 Originally Posted by James Heinrich It's harder to see from the data since many people (most?) will stop factoring immediately after finding a factor, so unless the factor pair is in the same class the second factor wouldn't be discovered.
Right. Depends on settings in this part of the mfaktc.ini (my default settings shown)
Code:
# Allow to split an assignment into multiple bit ranges.
# 0 = disabled
# 1 = enabled
# Enabled Stages make only sense when StopAfterFactor is 1 or 2.
# Do not change this in the middle of a run which spans over multiple
# bitlevels, in this case mfaktc will ignore the checkpoint file and
# restarts from the beginning.
#
# Default: Stages=1

Stages=1

# possible values for StopAfterFactor:
# 0: Do not stop the current assignment after a factor was found.
# 1: When a factor was found for the current assignment stop after the
#    current bitlevel. This makes only sense when Stages is enabled.
# 2: When a factor was found for the current assignment stop after the
#    current class.
#
# Default: StopAfterFactor=1

StopAfterFactor=1
Computing credit is given as if the setting was StopAfterFactor=2. (Which is less than the computing performed when StopAfterFactor=1, in the case of factor(s) found.)