Automatic kvetching about P-1, LL and DC work from GPU72 - Page 5

chalsall · 2013-03-21, 14:36

Quote:

Originally Posted by Aramis Wyler

Do we need to put our gpu72 password and username into the ProxyUser and ProxyPass entries when we change ProxyHost?

Nope.

And good question -- I'll add that to the FAQ post.

sdbardwick · 2013-04-23, 02:42

Ok, I can't figure out the work assignment rules.
The default for my PrimeNet account is LL, and all of my AVX capable boxes are set so all threads' worktypes are LL.
GPU72 shows all but one as being set to WMS; I am getting DC assignments.
I wonder what my non-AVX (currently ECM) boxes will get?

Is there some setting I don't know about?

chalsall · 2013-04-23, 13:46

Quote:

Originally Posted by sdbardwick

Is there some setting I don't know about?

Please see Q7 and A7 (which I just added) in the FAQ post above.

This has been talked about before elsewhere, but it should have been there as well.

sdbardwick · 2013-04-23, 15:56

Apparently you need to either individually set all worker windows to the same worktype or use the "All Workers" setting for the change to be effective. After the change is recorded on GPU72, you can then restore the threads to different worktypes which will be respected for assignments (at least for the LL/DC types I tested).

chalsall · 2013-04-23, 16:03

Quote:

Originally Posted by sdbardwick

Apparently you need to either individually set all worker windows to the same worktype or use the "All Workers" setting for the change to be effective. After the change is recorded on GPU72, you can then restore the threads to different worktypes which will be respected for assignments (at least for the LL/DC types I tested).

OK, thanks for that report.

I'll go through the logs (all Proxy messages are recorded for analysis) and see if there's a bug in my code, or if this is simply the nominal behavior in the API exchanges between Prime95/mprime and Primenet.

Edit: Just saw your edit... It will be the same behavior for all worktypes.

sdbardwick · 2013-04-23, 20:11

Damn, one really needs to wrangle with the worker settings to get the correct type of work (LL vs. DC), even when GPU72 says LL, and all worker threads are set to LL. I kept getting DCs until I changed workers to different types, communicated, changed types again, communicated, and finally set to same type and communicated.

For reference in the logs look at computers i7-2600K and Jupiter-3570K.
i5-2500k-test logs probably show the quickest resolution: Change a worker to DC, communicate, change the other worker to DC, communicate, use All Workers to change both to LL.

Edt: Forgot to mention that the CPUs with only one worker window behave better, IIRC.

Chuck · 2013-04-24, 00:18

Quote:

Originally Posted by sdbardwick

Damn, one really needs to wrangle with the worker settings to get the correct type of work (LL vs. DC), even when GPU72 says LL, and all worker threads are set to LL. I kept getting DCs until I changed workers to different types, communicated, changed types again, communicated, and finally set to same type and communicated.

Same thing happened to me a few months back when I set up a new laptop. It seemed mysterious until I changed worktypes as you described.

sdbardwick · 2013-05-01, 13:03

I'm done. Keep getting DCs rather than LL on random machines despite the same machines getting LL assignments previously. This just adds administrative overhead...

kladner · 2013-05-01, 15:19

I'm almost afraid to mention this and tempt fate, but I think I've finally gotten away from unwanted DC assignments. For the longest time I had been doing a work around on my third P-1 worker: moving assignments from other workers to avoid automatic assignments on #3. A few weeks back I went through a hardware shakeup which included a CPU change from a PhenomII x6 to an FX-8350 x8. That setup has run long enough for a number of automatic fetches through GPU72, and worker 3 has received only P-1's (so far.)

James Heinrich · 2013-05-13, 17:06

A minor observation: I noticed that gimps.gpu72.com formats assignment keys differently (uppercase vs lowercase) for GPU72-owned assignments vs passthrough requests. Assignments that GPU72 is interested in are returned in all-lowercase, and requests that are passed through to PrimeNet get all-uppercase assignment keys. For example:

Code:

Pfactor=bb266817ed297ce1e1fbb1079b0df7__,1,2,61559999,-1,73,2
Pfactor=741879D85394BC94352CE0C5EA0E50__,1,2,80015017,-1,73,2

Not that it really makes any difference, just an observation.

bayanne · 2013-10-09, 13:47

Is there anyone running a gpu on a Mac at present at GPU72?

Could do with a hand getting mine set up

Thanks

2013-04-23, 15:56	#48
sdbardwick Aug 2002 North San Diego County 5·137 Posts	Apparently you need to either individually set all worker windows to the same worktype or use the "All Workers" setting for the change to be effective. After the change is recorded on GPU72, you can then restore the threads to different worktypes which will be respected for assignments (at least for the LL/DC types I tested). Last fiddled with by sdbardwick on 2013-04-23 at 15:59

2013-04-23, 20:11	#50
sdbardwick Aug 2002 North San Diego County 1010101101₂ Posts	Damn, one really needs to wrangle with the worker settings to get the correct type of work (LL vs. DC), even when GPU72 says LL, and all worker threads are set to LL. I kept getting DCs until I changed workers to different types, communicated, changed types again, communicated, and finally set to same type and communicated. For reference in the logs look at computers i7-2600K and Jupiter-3570K. i5-2500k-test logs probably show the quickest resolution: Change a worker to DC, communicate, change the other worker to DC, communicate, use All Workers to change both to LL. Edt: Forgot to mention that the CPUs with only one worker window behave better, IIRC. Last fiddled with by sdbardwick on 2013-04-23 at 20:16

2013-05-13, 17:06	#54
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario 3·5·227 Posts	A minor observation: I noticed that gimps.gpu72.com formats assignment keys differently (uppercase vs lowercase) for GPU72-owned assignments vs passthrough requests. Assignments that GPU72 is interested in are returned in all-lowercase, and requests that are passed through to PrimeNet get all-uppercase assignment keys. For example: Code: Pfactor=bb266817ed297ce1e1fbb1079b0df7__,1,2,61559999,-1,73,2 Pfactor=741879D85394BC94352CE0C5EA0E50__,1,2,80015017,-1,73,2 Not that it really makes any difference, just an observation.

2013-10-09, 13:47	#55
bayanne "Tony Gott" Aug 2002 Yell, Shetland, UK 2²·83 Posts	GPU on a Mac Is there anyone running a gpu on a Mac at present at GPU72? Could do with a hand getting mine set up Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Automatic fetch of Trial Factoring work for GPU mfakt*	LaurV	GPU to 72	81	2020-12-02 05:17
GPU72 doesn't show all available DC work	Mark Rose	GPU to 72	2	2014-01-24 00:33
GPU72 proxy ignores work type changes	Bdot	GPU to 72	7	2013-12-18 22:21
New work types for GPU72?	chalsall	GPU to 72	72	2013-10-03 20:21
Completed 29M work not showing as completed in GPU72	Chuck	GPU to 72	2	2013-02-02 03:25

2013-04-23, 02:42	#46
sdbardwick Aug 2002 North San Diego County 5·137 Posts	Ok, I can't figure out the work assignment rules. The default for my PrimeNet account is LL, and all of my AVX capable boxes are set so all threads' worktypes are LL. GPU72 shows all but one as being set to WMS; I am getting DC assignments. I wonder what my non-AVX (currently ECM) boxes will get? Is there some setting I don't know about?

2013-05-01, 13:03	#52
sdbardwick Aug 2002 North San Diego County 1255₈ Posts	I'm done. Keep getting DCs rather than LL on random machines despite the same machines getting LL assignments previously. This just adds administrative overhead...

2013-05-01, 15:19	#53
kladner "Kieren" Jul 2011 In My Own Galaxy! 10011110101110₂ Posts	I'm almost afraid to mention this and tempt fate, but I think I've finally gotten away from unwanted DC assignments. For the longest time I had been doing a work around on my third P-1 worker: moving assignments from other workers to avoid automatic assignments on #3. A few weeks back I went through a hardware shakeup which included a CPU change from a PhenomII x6 to an FX-8350 x8. That setup has run long enough for a number of automatic fetches through GPU72, and worker 3 has received only P-1's (so far.)