[QUOTE=kracker;329152]MaxHighMemWorkers, 2, 3, or 4 what is the difference?[/QUOTE]

Sorry. I should have explained my settings more thoroughly. To recap:

In prime.txt:
"PauseWhileRunning=photoshop[3],bridge[3]"
I have a hex core Phenom II, running P-1 on all six. This line causes three workers to pause when either Photoshop or Adobe Bridge starts up, and resume when they quit.


"LowMemWhileRunning=photoshop,bridge"
This makes the remaining workers switch to Stage 1 work if any of them is running Stage 2. When P'shop and/or Bridge shut down, S2 work will resume, though not necessarily on the same workers as before.

In local.txt:
"MaxHighMemWorkers=4"
This limits the number of workers which can be in Stage 2 at the same time. This allows more memory to be allocated to each instance in S2. Stage 1 completes more quickly than Stage 2. If the number of HighMemWorkers is half or less of the total workers, you will build up a backlog of assignments with S1 completed which are waiting for an opening on the S2 front. At some point then, you have to do something to let that backlog get processed. On the other hand, if the number of HighMemWorkers is greater than half of the total there is a good chance that the S2's will keep up with the S1's.

[QUOTE=kladner;329178]Sorry. I should have explained my settings more thoroughly. To recap:

In prime.txt:
"PauseWhileRunning=photoshop[3],bridge[3]"
I have a hex core Phenom II, running P-1 on all six. This line causes three workers to pause when either Photoshop or Adobe Bridge starts up, and resume when they quit.


"LowMemWhileRunning=photoshop,bridge"
This makes the remaining workers switch to Stage 1 work if any of them is running Stage 2. When P'shop and/or Bridge shut down, S2 work will resume, though not necessarily on the same workers as before.

In local.txt:
"MaxHighMemWorkers=4"
This limits the number of workers which can be in Stage 2 at the same time. This allows more memory to be allocated to each instance in S2. Stage 1 completes more quickly than Stage 2. If the number of HighMemWorkers is half or less of the total workers, you will build up a backlog of assignments with S1 completed which are waiting for an opening on the S2 front. At some point then, you have to do something to let that backlog get processed. On the other hand, if the number of HighMemWorkers is greater than half of the total there is a good chance that the S2's will keep up with the S1's.[/QUOTE]

Ahh, I get it now, tnx! :smile:

Just a status update...

At the suggestion of Jerry, I have added a new field to the LLTF and DCTF forms: GHz Days of work.

How this works is if a number is entered here (>0), the "Number of assignments" field will be ignored, and instead the requested number of GHz Days of work will be assigned (up to the nominal limit of assignments allowed per request; 100 for most people). Please note that at least one assignment will be issued, even if it's more than the GHzDays field specifies.

This is largely intended for spider use, but if anyone would like to see this implemented on the other forms (e.g. LL P-1) please let me know.

Also, Aramis... You will be pleased to know that (at least here) programmers listen to their users. Scott has come up with an elegant solution which will hopefully avoid any confusion for MISFIT users.

Lastly, I'm continuing to monitor the assignment load on Primenet. Yesterday the assignment count went back up to about 1,000 a day. If needed, I'll lower the Pledge level back down to 72 to ensure we're ready to release at that level. Also, the "What Makes Sense" option has changed to mean "Lowest TF Level" from "Lowest Exponent". The thinking is to ensure that the candidates at 72 bits are not reassigned to go to 73, so they will remain available to release back to Primenet if needed.

GPU72.com out.

I took a break from my usual LMH-TF work and LLTF'd 100 exponents 71-72, found 3 factors. If the demand remains high I can chew through another 100.

[QUOTE=James Heinrich;329365]I took a break from my usual LMH-TF work and LLTF'd 100 exponents 71-72, found 3 factors. If the demand remains high I can chew through another 100.[/QUOTE]

Please.

I've grabbed 200 then.

[QUOTE=James Heinrich;329367]I've grabbed 200 then.[/QUOTE]

Thanks!

What is more useful[SIZE=1](et needed)[/SIZE]? 70 to 71, 71 to 72, etc?
(right at the moment)

[SIZE=1][COLOR=Silver] EDIT: w00t looks like one of my laptops found a P-1 factor a[SIZE=1] hour or so ago.[/SIZE][/COLOR][/SIZE]

[QUOTE=kracker;329394]What is more useful[SIZE=1](et needed)[/SIZE]? 70 to 71, 71 to 72, etc?
(right at the moment)[/QUOTE]

Anything going to 72.

[QUOTE=chalsall;329395]Anything going to 72.[/QUOTE]

Thanks. :max:

It might be a good idea to lower the default pledge level back to 72 bits right now.