More work for my "workers"
 

On my dual core CPU PC one prime95 worker is doing trial factoring (the other LL tests). GIMPS give me at most 15 exponents for trial factoring. Clearing one exponent takes one and a half hours in the average. This means 16 exponents per day. When I go abroad on a weekend trip I leave my PC working but want it to be disconnected to the web. How can I get e.g. 50 exponents from GIMPS as to avoid my TF-worker will be running out of work?

Konrad Remus

From the menu, under "Options", select "Preferences", change the "Days of work to queueup" to a suitable number.
Next step, in your "Prime.txt" file add the line:

MaxExponents=50

I have got the same "issue" on my Core2 Duo pc. (Lone Mersenne Hunting)
I first set my "Days of work to queueup" to up 15 then 30
but I only got a measily 20-30 numbers to crunch per core.

Is this normal behaviour???

[QUOTE=CedricVonck;148063]I have got the same "issue" on my Core2 Duo pc. (Lone Mersenne Hunting)
I first set my "Days of work to queueup" to up 15 then 30
but I only got a measily 20-30 numbers to crunch per core.

Is this normal behaviour???[/QUOTE]

From readme.txt

[CODE]
TEST MENU
---------

The PrimeNet menu choice lets you configure the type of work you get
from the server. The "Use PrimeNet..." option can be turned on to
switch from the manual method to the automatic method.
The "Request whatever..." box should be left checked. However, if you
are running a slow computer and don't mind waiting several months for
a single Lucas-Lehmer test to complete OR you are running a faster
computer and would rather do factoring, then uncheck this box and
choose a different type of work to do. The "Always have at least
this many days of work queued up" value should be changed based on
how often you connect to the Internet. As long as you connect at least
once in the given time period, prime95 will have an uninterrupted stream
of work. However, the program will not checkout more than 20 exponents
no matter what this value is set at.[/CODE]

HOWEVA

from undoc.txt

[CODE]
The program will restrict how many exponents can be added to worktodo.txt.
To override this, change prime.txt:
MaxExponents=n[/CODE]

[QUOTE=Kevin;148074][CODE]
The program will restrict how many exponents can be added to worktodo.txt.
To override this, change prime.txt:
MaxExponents=n[/CODE][/QUOTE]
[B]echo[/B], echo, [COLOR="DimGray"]echo[/COLOR], [COLOR="Silver"]echo[/COLOR]

[QUOTE=Kevin;148074]HOWEVA

from undoc.txt

[CODE]
The program will restrict how many exponents can be added to worktodo.txt.
To override this, change prime.txt:
MaxExponents=n[/CODE][/QUOTE]

Well I have MaxExpoents=50
Day of work to queue up: 30

and I am still only getting 15 LMH assignments the last of which will be finished NOT 30 days but 30 HOURS from now. Each time it completes 1 I get one more.

[QUOTE=petrw1;148303]Well I have MaxExpoents=50
Day of work to queue up: 30

and I am still only getting 15 LMH assignments the last of which will be finished NOT 30 days but 30 HOURS from now. Each time it completes 1 I get one more.[/QUOTE]This is not what I observe on my machines. How many cores do you have ? I suspect the variable is MaxExponents if for all cores together, but, neither tested this hypotheses, nor checked in the sources. Did you restart the program after changing prime.txt. Finally did you notice the typo in your post : "MaxExpoents=50", this should be : "MaxExpo[b]n[/b]ents=50"

Jacob

perhaps you need to set UnreserveDays to be higher? (prime95 probably thinks the last exponent will start after 30 days.
[quote]
Normally, the program will unreserve an exponent if it is scheduled to start
thirty days after the Test/Primenet Days of work to get value. You can adjust
this interval by setting in prime.txt:
UnreserveDays=n
where n is the number of days. You should increase this value if you are
loading up worktodo.txt with a large amount of work and do not want any of
the work to be unreserved.
[/quote])

[QUOTE=S485122;148317]This is not what I observe on my machines. How many cores do you have ? I suspect the variable is MaxExponents if for all cores together, but, neither tested this hypotheses, nor checked in the sources. Did you restart the program after changing prime.txt. Finally did you notice the typo in your post : "MaxExpoents=50", this should be : "MaxExpo[b]n[/b]ents=50"

Jacob[/QUOTE]


PIII 866 Mhz (long before the days of multiple cores)
I believe I only spelled it wrong in the post but then when I rechecked prime.txt just now the line was gone so maybe I spelled it wrong and prime95 removed the line. I just put it back spelled right this time (I promise) and I will see what happens.

[QUOTE=petrw1;148370]PIII 866 Mhz (long before the days of multiple cores)
I believe I only spelled it wrong in the post but then when I rechecked prime.txt just now the line was gone so maybe I spelled it wrong and prime95 removed the line. I just put it back spelled right this time (I promise) and I will see what happens.[/QUOTE]Make sure you stop and exit Prime95, then edit prime.txt