GPU to 72 status...

[chalsall]

Originally Posted by Uncwilly

It used to. It takes selecting Lowest Exponent (or the like) to get it to update. Don't know if this is feature or not.

Thanks for pointing that out... I added a $Low = 66000000 for WMS and LGD, so we would focus on the Cat4 range for a while. I didn't realize this would screw up the WMS for the 332M range. This has been fixed.

[James Heinrich]

Originally Posted by James Heinrich

The "Work Done By <Username>" graph X axis labels are running over each other:
http://www.gpu72.com/graphs/worker/5...08c88b2ba9578/

Dredging this up from 5 months ago because it's still not fixed

[manfred4]

Currently the smallest available Cat4 assignment is in the 73M - I think you should be releasing some more exponents / reserve further ranges for TF.

[chalsall]

Originally Posted by manfred4

Currently the smallest available Cat4 assignment is in the 73M - I think you should be releasing some more exponents / reserve further ranges for TF.

Not true. The highest which appears on Primenet's summary page is in the 71M range, not 73M.

And few (if any) are actually being assigned there, and none not TFed below 73 "bits"

"Spidy" is doing its job, and pulling its "rip-cord" as needed. Please see the below as an example of what Spidy does every five minutes.

20140416_184001 INFO:  Get Manual Work spider starting...
20140416_184002 INFO:  PM-1...
20140416_184003 INFO:  100: 66293263,73,0 (7ED910084013041CAE74C7518DAA8E83) -- Keep: 0
20140416_184003 INFO:  100: 66293267,73,0 (9C8839A5E63E3550F667035741F4A717) -- Keep: 0
20140416_184003 INFO:  100: 66293323,73,0 (C22548FD2A14050435B61B40CEA04EA4) -- Keep: 0
20140416_184003 INFO:  100: 66293327,73,0 (20FC45A3EE5609E52401239D2AAC214C) -- Keep: 0
20140416_184003 INFO:  100: 66293329,73,0 (4D58086875138668AD2C7A0EF83F4D0D) -- Keep: 0
20140416_184003 INFO:  100: 66293443,73,0 (B2A29909FAB5BB3A5D1200CDF305FCB8) -- Keep: 0
20140416_184003 INFO:  100: 66293497,73,0 (618AC794092FF9FE434FE034DF2529BC) -- Keep: 0
20140416_184003 INFO:  100: 66293509,73,0 (DFAC94852BF160DAF526EA8079671A50) -- Keep: 0
20140416_184003 INFO:  100: 66293533,73,0 (01F6E1BAB473B01E4C41687F8B93F5C7) -- Keep: 0
20140416_184003 INFO:  100: 66293587,73,0 (106CC4D73A00FD4A91C4589C4DFFBC01) -- Keep: 0
20140416_184003 INFO:  Category 3...
20140416_184004 INFO:  100: 61576939,74,1 (67323B64EA5E7E47CF54EDC1CB2B53D3) -- Keep: 0
20140416_184004 INFO:  100: 61577057,74,1 (8332D7FF0625880002427E3ED023C127) -- Keep: 0
20140416_184004 INFO:  100: 61581893,74,1 (104128B156C06CFE01A26C27267DAA7E) -- Keep: 0
20140416_184004 INFO:  100: 61582271,74,1 (0EB8B8B2CE656A79A3F7C92DBD52059F) -- Keep: 0
20140416_184005 INFO:  100: 61638259,74,1 (7BA3C053E3EA8FA3FE161BC04B36B8EF) -- Keep: 0
20140416_184005 INFO:  100: 61650319,74,1 (D8BB15005C2969027EC88848D9018B7F) -- Keep: 0
20140416_184006 INFO:  100: 61659019,74,1 (1D1D33F34D2DEAF99EBD86BD1D373E70) -- Keep: 0
20140416_184006 INFO:  100: 61659469,74,1 (E14E9CEFDCDFFF0EE0CCB77E38B19474) -- Keep: 0
20140416_184006 INFO:  100: 61662421,74,1 (182FCFDC3A27C93FCD4A603191F08A14) -- Keep: 0
20140416_184006 INFO:  100: 61662551,74,1 (85BB5E16395746BB324782EAB588E209) -- Keep: 0
20140416_184007 INFO:  100: 61665839,74,1 (6757E159A94367BE29C8A6CA5E0C7584) -- Keep: 0
20140416_184007 INFO:  100: 61695509,74,1 (77E235F1FF1C07EB765A8043EEECE1CC) -- Keep: 0
20140416_184007 INFO:  Category 4...
20140416_184008 INFO:  100: 66293701,73,0 (72D077F239B35613078036CFA12720B6) -- Keep: 0
20140416_184008 INFO:  100: 66293737,73,0 (2AB4B2CC3E128E0CA9F7E3431AAC0FD1) -- Keep: 0
20140416_184008 INFO:  100: 66293743,73,0 (8331B79691403033B461618BEF239222) -- Keep: 0
20140416_184008 INFO:  100: 66293789,73,0 (05E55AB2AB6158AA26FFE10416B3F033) -- Keep: 0
20140416_184009 INFO:  100: 66293803,73,0 (04C1C6E7B04EA6C8B87B47BF2667B116) -- Keep: 0
20140416_184009 INFO:  100: 66293809,73,0 (1C6C4EEA62B196A9A1D5BE3321C2E750) -- Keep: 0
20140416_184009 INFO:  100: 66293947,73,0 (29DB3381848947A04F1CEC13FD13B617) -- Keep: 0
20140416_184009 INFO:  100: 66294023,73,0 (CEB4376D23C7506AA51B3AABB9E404E9) -- Keep: 0
20140416_184010 INFO:  100: 66294061,73,0 (BE158DF1FE1BE89CF882D02314AB463C) -- Keep: 0
20140416_184010 INFO:  100: 66294091,73,0 (CF90A493FB8E1FD89A019D1190F0338F) -- Keep: 0
20140416_184011 INFO:  100: 66294113,73,0 (A831071BA7BCD24F11C9CDBE8111EA91) -- Keep: 0
20140416_184011 INFO:  100: 66294161,73,0 (CC6D0868671E3C6E642AD9B856018745) -- Keep: 0
20140416_184011 INFO:  100: 66294187,73,0 (2A25229404CD57BF435518ACF2157729) -- Keep: 0
20140416_184011 INFO:  100: 66294313,73,0 (A2773DFD40CE733B0FC04912B9987B32) -- Keep: 0
20140416_184012 INFO:  100: 66294367,73,0 (2752CB3FE05BE3DA15B224D2385A777C) -- Keep: 0
20140416_184012 INFO:  100: 69117583,73,1 (A61AAA863D6024B38479CD4243871734) -- Keep: 0
20140416_184013 INFO:  100: 69171917,73,1 (34259FD203FD6B771F65CF677AA65817) -- Keep: 0
20140416_184013 INFO:  100: 69306617,73,1 (7B208DB82B95A5C46A8EEF75F20B4CD0) -- Keep: 0
20140416_184014 INFO:  100: 69703369,74,1 (5C4446C9D837C71C7BD2A2050D64B82F) -- Keep: 0
20140416_184014 INFO:  100: 69882523,73,1 (D2B7EA0277947F42BF53A30531B847E7) -- Keep: 0
20140416_184014 INFO:  100: 69889487,73,1 (2DB7B30446101929A81DB6A0CC152CB7) -- Keep: 0
20140416_184014 INFO:  100: 69894533,74,1 (54D41F8F384E69D859BAAC0738C6C880) -- Keep: 0

Edit: And just so you all know, the "Keep: 0" at the end of each line means the assignment(s) will be returned to Primenet within 60 seconds.

[James Heinrich]

Just noticed a tiny thing on /account/getassignments/lltf/ (not sure if applies to other assignment types). On pageload the Will Factor To box is set to "73". If you change to "Let GPU72 Decide" it changes to 74, if you change to "LMH Depth-first" it changes to 78. But if you change back to "What makes sense" it doesn't revert to 73.

Would appear to be controlled in /js/assign_preview.js::DoOption()

[TheMawn]

Just an early heads up, but I'll remind you later...

From Friday May 16 to Monday May 26, I will be on another continent so my CPU and more importantly both GPUs will be down for 10 days @ 600 GHz-Days per day.

[Uncwilly]

Originally Posted by TheMawn

Just an early heads up, but I'll remind you later...

From Friday May 16 to Monday May 26, I will be on another continent so my CPU and more importantly both GPUs will be down for 10 days @ 600 GHz-Days per day.

You could run a few handfuls of 332M numbers up to 82 or 83 during that time. Would not make a big results file. (Just take any early ones, or ones that are already at 76 or above.)

[James Heinrich]

Originally Posted by Uncwilly

You could run a few handfuls of 332M numbers up to 82 or 83 during that time. Would not make a big results file. (Just take any early ones, or ones that are already at 76 or above.)

I think the issue was more that his system would be off, rather than suffering from lack of maintenance for 10 days. For 10 days I can even pre-feed my systems doing >1G TF where exponents are completed (quite literally) every 2 seconds.

[James Heinrich]

Originally Posted by James Heinrich

In celebration of (unexpectedly) getting a second GTX 670 today, I'll take a break from my usual project and pick up 200 candidates (100 for each 670).

This is getting weird. I've completed about 90 assignments (67M, 71-73) on each 670, and my old 670 has found 6 factors and the new (to me) 670 has found none. I think it's just random chance that put all the factorable assignments on the first GPU; the second one passes the self-test and did indeed find one of the factors I found on the other GPU when I was getting suspicious. But odd.

[TheMawn]

Originally Posted by James Heinrich

the second one passes the self-test and did indeed find one of the factors I found on the other GPU when I was getting suspicious.

Then you're probably fine. I get streaks like that too and they freak me out a bit also. It definitely isn't worth double-checking even if the GPU is known to miss the odd factor.

If I'm ever that bored, I might see if I could learn how to make mfaktx run a few thousand exponents with factors on only the class that contains that factor. It would be fast as hell and a person could get a meaningful success rate.

[James Heinrich]

Originally Posted by TheMawn

Then you're probably fine. I get streaks like that too and they freak me out a bit also.

Normally I wouldn't think much of it. It's just that I just got this "new" video card from a friend who upgraded to a 780ti, and it hasn't (ever) found any previously-unknown factors, so I'm just cautious.

Originally Posted by TheMawn

If I'm ever that bored, I might see if I could learn how to make mfaktx run a few thousand exponents with factors on only the class that contains that factor. It would be fast as hell and a person could get a meaningful success rate.

That's what the self-test does. I believe the automatic selftest that runs every time you start mfaktc has 92 exponents with known factors, you can also run two levels of extended self-test, per the help:

-h                     display this help and exit
-d <device number>     specify the device number used by this program
-tf <exp> <min> <max>  trial factor M<exp> from 2^<min> to 2^<max> and exit
                       instead of parsing the worktodo file
-st                    run builtin selftest (1557 testcases) and exit
-st2                   run builtin selftest (all testcases) and exit
-v <number>            set verbosity (min = 0, default = 1, max = 2)