If we dropped it to 20 a day from 120 we could still keep up (and slowly build buffer) and still head towards the goal of 100,000 ahead. That sounds preferable to me. We would theoretically save about two tests per month if 7% are completed on first assignment. Not a huge amount, but it would come for free by slowing down the growth until we have more LLTF capacity. It would take 3 years instead of 6 months to reach the 100,000 ahead goal.

How many a day can one card do? Two 590s were added above. That should make a fair difference AFAIK.

and hopefully soon we have the next version of mfakto which process tf74 faster and hopefully supports intel hd4* chips... however fast those may be...

[QUOTE=henryzz;384073]How many a day can one card do? Two 590s were added above. That should make a fair difference AFAIK.[/QUOTE]
Overall they did 48 in the last 24 hours. I had to stop one gpu on one of the cards, as the system froze when using both.

[QUOTE=blip;384075]Overall they did 48 in the last 24 hours. I had to stop one gpu on one of the cards, as the system froze when using both.[/QUOTE]

Hmm, well with my system with the 690 (amd 4800+) I have to keep the cpu busy otherwise it freezes between 1-18hours..

[QUOTE=blip;384075]Overall they did 48 in the last 24 hours. I had to stop one gpu on one of the cards, as the system froze when using both.[/QUOTE]

Even so, 1.5 GTX 590's should give about 1 THz-d/day. That's about 25% of what we're currently short (71 -> 74). Granted, there are a lot of exponents sitting at 73 bits, so in the meantime that will provide almost half the needed 73->74 capacity.

Let's say we release 25,000 CAT4 candidates at 73bits (to get to the 100,000).
With only 7% completing (assuming GPU72 gets them back afterwards), of which ~1/74 would have a factor between 73-74bits.
In that case we'll only have 'missed' about 24 factors.
Looking at it that way I'm inclined to say releasing CAT4 at 73bits for the time being is not a big deal.

We all knew the new assignment rules would come at a cost. A few less candidates saved by TF and more triple checks is that cost to advance milestones faster in the future.

[QUOTE=NickOfTime;384074]and hopefully soon we have the next version of mfakto which process tf74 faster and hopefully supports intel hd4* chips... however fast those may be...[/QUOTE]

It already supports Intel onboard HD4***.

[QUOTE=legendarymudkip;384113]It already supports Intel onboard HD4***.[/QUOTE]

Not yet? There is a -pre version which works... but they are _not_ for actual production.

[QUOTE=kracker;384118]Not yet? There is a -pre version which works... but they are _not_ for actual production.[/QUOTE]

I'd forgotten that... But it still passes the selftest and (as far as I know) no bug has been found that means it finds bad results.

[QUOTE=legendarymudkip;384120]I'd forgotten that... But it still passes the selftest and (as far as I know) no bug has been found that means it finds bad results.[/QUOTE]

Yes and no, Bdot told me that some factors have a rare chance of being missed even if the full selftest had passed. The latest code on github is fine I think, but the last -pre build on the mfakto thread had that bug. (Only on Intel HD I think)