GPU to 72 status... - Page 242

TheMawn · 2014-01-29, 06:11

This also means if you submit in too large a batch, the server will time out before it reaches your factors found. If you're not careful, you might go into your results file and delete everything above the last processed entry... deleting all your factors found in the process.

Axelsson · 2014-01-30, 18:11

TheMawn, that probably explains it, I got the tail end of factors from someone that accidentally deleted a bunch of factors after a timeout during reporting.

The ten factors I found was from the ten candidates I ran in 87M, it isn't a result of primenet sorting the results. I just used the result report to find the factors again, my log files are long gone.

Göran

LaurV · 2014-01-31, 04:33

Well, they are all in 67 bits, so, from here, it is not difficult to see who the unlucky guy was Freaks32, last year in March . You also did plenty of 66 and 67 there, too, before, hehe.

LaurV · 2014-01-31, 04:53

Quote:

Originally Posted by TheMawn

This also means if you submit in too large a batch, the server will time out before it reaches your factors found. If you're not careful, you might go into your results file and delete everything above the last processed entry... deleting all your factors found in the process.

Right. In this case (not all factors digested by the server), you should *not delete anything* and just retry submission. Processing "no need" results is about 5-10 times faster for the server (this is not a WAG! it can be easily seen experimentally, and the explanation is probably related to the fact that in case of "no need" result, the DB is read and the error 40 is generated, but in case on "ok" result, the DB must be changed also, which takes longer) so it will go further in your list. Every time you report, you will get a couple of "error 40" or so, but it will go deeper in your list, about double the first pass. In 3, 4, 5 trials you can send whole bunches. Faster if you do not try to send during peak times when the reports are generated. I did this daily, before the Misfit era (and before having my own scripts, which I scrapped for Misfit), when I used to manually report the results. I used to send the same reports few times, until I could see the factors on screen, at the end of the report. Then only, I was deleting the files.

TheMawn · 2014-01-31, 05:35

My own method is to break the results file into smaller chunks using copypasta. During my last 400M 65 to 68 spree, I would break the files into chunks of roughly 80 KB with an absolute maximum of 100 KB and only once in a while I would get a timeout. About 3 files per GPU per day.

I would argue that the "result not needed" files get processed more than ten times faster. However, everything else I did was the same. Make sure that the factors at the bottom of the page showed up properly, then delete the small file chunk.

For completeness, I re-checked the server for exponents below 68 in the range I did and I found five or six, which were probably reserved when I grabbed the work.

LaurV · 2014-01-31, 08:30

Quote:

Originally Posted by TheMawn

My own method is ...

"is"? Not "was"? Do you mean you don't use Misfit yet? Linux? hehe...

bayanne · 2014-02-01, 06:16

Chris Halsall

A factor was found for M44036591 between 70:71 it just has not been reported due to ongoing glitch, so your spider may decide to reallocate it.

Just flagging it up so you can take it out to save it being trial factored again ...

kracker · 2014-02-01, 20:39

Quote:

Originally Posted by LaurV

"is"? Not "was"? Do you mean you don't use Misfit yet? Linux? hehe...

MISFIT FTW!

chalsall · 2014-02-01, 21:10

Quote:

Originally Posted by bayanne

A factor was found for M44036591 between 70:71 it just has not been reported due to ongoing glitch, so your spider may decide to reallocate it.

Just flagging it up so you can take it out to save it being trial factored again ...

Thanks for the heads up, but not to worry -- Primenet started accepting "Factor Found" results again.

Also, so you know, TF assignments are now very rarely automatically recycled -- the system will patiently wait for the assigned work to be finished. (I, on the other hand, am not as patient

, and will often PM or e-mail the assignee asking for them to complete (or release) assignments which have been out for more than two months.)

TheMawn · 2014-02-07, 00:03

By the way, how is the DC-TF effort going? With the primenet summary page looking a lot better, I see a big lot of "assigned" TF work. Are there charts yet to show us how the progress is, or if any 70 bits exponents are being released?

LaurV · 2014-02-07, 03:05

It's going, it's going. I am putting 1.5THzDays/Day into it. I may double it soon, if it does not get too hot here (Thai summer starts around March; the hottest month of the year is April). Other people do even better, i.e. they are putting more THzDays into the effort. We can keep the advance. We have the resources. The only thing we are missing right now, is the motivation... err... em.. we are not so convinced that the effort is worth (where is davieddy?

). If you read my older posts, I mean to TF the 33M to 71, we have one chance in ~71 to find a factor for the exponents which are not P-1, but one in ~100 to get a factor for the exponents with P-1 done to the usual B1/B2 limits. And if you check these tables (the second one), you see I am right with the calculus. We only get one factor in a hundred trials, or 1% success rate. Now, a good GPU do about 65-75 of those per day, but it need one full day (~25 hours) to run the DC test. So, technically we are slower, about 30-40% behind the schedule by continuing to TF the 33-34M to 71. We may be better doing TF to 70 only, and then do DCLL, especially for the exponents with P-1 done. James' graphs [edit: btw, they still don't work! (they show a white screen) someone should check those google charts! see my former posts] do not take into the account the fact that P-1 was done, but only if it is first time LL, or DCLL).

Of course, finding factors is cool, and irrevocable clears the exponents. So people prefer to invest a bit more in factoring right now. We still cleared more than we could DCLL since we started DCTF last week, by a very narrow margin, but as I said, we might have been lucky

We will maintain the status quo for a while, at least till the heat hits or till chalsall gets pissed on us.

2014-01-31, 04:33	#2654
LaurV Romulan Interpreter Jun 2011 Thailand 7×1,373 Posts	Well, they are all in 67 bits, so, from here, it is not difficult to see who the unlucky guy was Freaks32, last year in March . You also did plenty of 66 and 67 there, too, before, hehe. Last fiddled with by LaurV on 2014-01-31 at 04:40 Reason: added spoiler

2014-02-07, 03:05	#2662
LaurV Romulan Interpreter Jun 2011 Thailand 7×1,373 Posts	It's going, it's going. I am putting 1.5THzDays/Day into it. I may double it soon, if it does not get too hot here (Thai summer starts around March; the hottest month of the year is April). Other people do even better, i.e. they are putting more THzDays into the effort. We can keep the advance. We have the resources. The only thing we are missing right now, is the motivation... err... em.. we are not so convinced that the effort is worth (where is davieddy? ). If you read my older posts, I mean to TF the 33M to 71, we have one chance in ~71 to find a factor for the exponents which are not P-1, but one in ~100 to get a factor for the exponents with P-1 done to the usual B1/B2 limits. And if you check these tables (the second one), you see I am right with the calculus. We only get one factor in a hundred trials, or 1% success rate. Now, a good GPU do about 65-75 of those per day, but it need one full day (~25 hours) to run the DC test. So, technically we are slower, about 30-40% behind the schedule by continuing to TF the 33-34M to 71. We may be better doing TF to 70 only, and then do DCLL, especially for the exponents with P-1 done. James' graphs [edit: btw, they still don't work! (they show a white screen) someone should check those google charts! see my former posts] do not take into the account the fact that P-1 was done, but only if it is first time LL, or DCLL). Of course, finding factors is cool, and irrevocable clears the exponents. So people prefer to invest a bit more in factoring right now. We still cleared more than we could DCLL since we started DCTF last week, by a very narrow margin, but as I said, we might have been lucky We will maintain the status quo for a while, at least till the heat hits or till chalsall gets pissed on us. Last fiddled with by LaurV on 2014-02-07 at 03:14

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Status	Primeinator	Operation Billion Digits	5	2011-12-06 02:35
62 bit status	1997rj7	Lone Mersenne Hunters	27	2008-09-29 13:52
OBD Status	Uncwilly	Operation Billion Digits	22	2005-10-25 14:05
1-2M LLR status	paulunderwood	3*2^n-1 Search	2	2005-03-13 17:03
Status of 26.0M - 26.5M	1997rj7	Lone Mersenne Hunters	25	2004-06-18 16:46

2014-01-29, 06:11	#2652
TheMawn May 2013 East. Always East. 11·157 Posts	This also means if you submit in too large a batch, the server will time out before it reaches your factors found. If you're not careful, you might go into your results file and delete everything above the last processed entry... deleting all your factors found in the process.

2014-01-30, 18:11	#2653
Axelsson Jul 2012 Sweden 2·3·7 Posts	TheMawn, that probably explains it, I got the tail end of factors from someone that accidentally deleted a bunch of factors after a timeout during reporting. The ten factors I found was from the ten candidates I ran in 87M, it isn't a result of primenet sorting the results. I just used the result report to find the factors again, my log files are long gone. Göran

2014-01-31, 05:35	#2656
TheMawn May 2013 East. Always East. 11·157 Posts	My own method is to break the results file into smaller chunks using copypasta. During my last 400M 65 to 68 spree, I would break the files into chunks of roughly 80 KB with an absolute maximum of 100 KB and only once in a while I would get a timeout. About 3 files per GPU per day. I would argue that the "result not needed" files get processed more than ten times faster. However, everything else I did was the same. Make sure that the factors at the bottom of the page showed up properly, then delete the small file chunk. For completeness, I re-checked the server for exponents below 68 in the range I did and I found five or six, which were probably reserved when I grabbed the work.

2014-02-01, 06:16	#2658
bayanne "Tony Gott" Aug 2002 Yell, Shetland, UK 2²×83 Posts	Chris Halsall A factor was found for M44036591 between 70:71 it just has not been reported due to ongoing glitch, so your spider may decide to reallocate it. Just flagging it up so you can take it out to save it being trial factored again ...

2014-02-07, 00:03	#2661
TheMawn May 2013 East. Always East. 11×157 Posts	By the way, how is the DC-TF effort going? With the primenet summary page looking a lot better, I see a big lot of "assigned" TF work. Are there charts yet to show us how the progress is, or if any 70 bits exponents are being released?