We helped find M48 22 days earlier.
 

I thought some here might like to know...

We as a group found 4,046 LL factors below 57,885,161 before Curtis was assigned it 2012.12.12. With the Primenet rate of LLing at approximately 183 a day over the last six months, that means we helped find M48 approximately 22 days earlier than it might have otherwise been.

Also, the exponent did pass through the system -- Jerry TFed it from 72 to 73 on 2012.10.07, so I think it's appropriate that he was also named in the announcement (although as a DCer).

Thanks for all the work everyone!!! :smile:

Thanks for your work on the system! It's our pleasure and finding M48 is exactly why we're here. :smile:

Congrats, Jerry, for having a direct role in this one. Way cool! :cool:

So everyone knows, I've turned off most of GPU72's spidering of Primenet for the time being, so submitted results won't be "observed" for a little while.

She's got enough to deal with.... :smile:

:razz:

[QUOTE=flashjh;327818]:razz:[/QUOTE]

Oh, I see.... Jerry is now Mr. Bigshot



And yes.... I joined gpu72 to increase sales of MISFIT.... Let the $$$$ roll in! :ignore:

[QUOTE=swl551;327858]Oh, I see.... Jerry is now Mr. Bigshot[/QUOTE]

I don't read anything like that into that.

Thankfully, no. I actually wasn't trying to just :razz:, I wanted it to say "Now why would you need to do that? :razz:, but my Android phone wouldn't keep the text in the block.

It was pretty cool to have 'touched' M48, now if I could just LL all the exponents that I TF :smile:

[QUOTE=flashjh;327869]Thankfully, no. I actually wasn't trying to just :razz:, I wanted it to say "Now why would you need to do that? :razz:, but my Android phone wouldn't keep the text in the block.

It was pretty cool to have 'touched' M48, now if I could just LL all the exponents that I TF :smile:[/QUOTE]

Now if any of us could do that, we'd find a prime next month or something ridiculous :cool:


(By the way, I interpret "bigshot" to mean something like "got your name on the press release". So, how does it feel to be a bigshot? :smile:)

[QUOTE=flashjh;327869]Thankfully, no. I actually wasn't trying to just :razz:, I wanted it to say "Now why would you need to do that? :razz:, but my Android phone wouldn't keep the text in the block.

It was pretty cool to have 'touched' M48, now if I could just LL all the exponents that I TF :smile:[/QUOTE]

C'mon: I was being sarcastic... and / or funny. No insult intended.

I love [URL="http://www.mersenne.info/trial_factored_bar_graph_video/3/332000000/"]this video[/URL]... It might be the time for a remake, or extension... (as I just finished the third marathon - moving everything to 71). Chris? :razz:

[QUOTE=LaurV;328010]I love [URL="http://www.mersenne.info/trial_factored_bar_graph_video/3/332000000/"]this video[/URL]... It might be the time for a remake, or extension... (as I just finished the third marathon - moving everything to 71). Chris? :razz:[/QUOTE]

OK. The job is running now. It will take a couple of days to complete.

[QUOTE=chalsall;328051] ...days... [/QUOTE] :shock::surprised:loco: I am really sorry! I didn't know is so much time consuming! I just imagined you take the ~300 missing frames and put all together...

[QUOTE=LaurV;328055]:shock::surprised:loco: I am really sorry! I didn't know is so much time consuming! I just imagined you take the ~300 missing frames and put all together...[/QUOTE]

Sure. But for the "level 3 zoom" the script has to do that for 1,000 different ranges....

:blush: sure, is nice to do all ranges. I was selfishly thinking only to the range I mentioned. Maybe the current LL and DC fronts too, but the other ranges did not have so much movement in the last 6 months.

[QUOTE=chalsall;327756]Jerry TFed it from 72 to 73 on 2012.10.07, so I think it's appropriate that he was also named in the announcement (although as a DCer)[/QUOTE]
I wonder if George picked Jerry to do the DC because he had already helped???

[QUOTE=rcv;328075]I wonder if George picked Jerry to do the DC because he had already helped???[/QUOTE]

I think it's more because he's the most active forum goer with a 580. :smile:

[QUOTE=Dubslow;328077]I think it's more because he's the most active forum goer with a 580. :smile:[/QUOTE]

At least two of them, in fact... He ran CUDALucas on two 580s in parallel to compare residues.

[QUOTE]No insult intended.[/QUOTE]

I know :smile:

12 factors in one day :) 8 - 33M and 4 - 61M out of 300 tested exponents. I think I hit the jackpot!

Time to buy a lottery ticket?

[QUOTE=chalsall;328051]OK. The job is running now. It will take a couple of days to complete.[/QUOTE]
Already visible, the first ~2000 done (first 3 levels seems to be completed, 1+10+100+1000=1111 movies already). The 332M (on the level 4) is not done yet. But I really like [URL="http://www.mersenne.info/trial_factored_bar_graph_video/0/0/"]the big view[/URL]! Wonderful job all workers/helpers, and wonderful job Chris to make the videos. I feel that I will do a lot of traffic to you (and to my inet provider) today... :razz:

There seems to be something odd with the underlying data (lying data?): [URL="http://www.mersenne.info/exponent_status_line_graph/2/30000000/"]30M.[/URL] Drilling down also shows the exponents not even first-time-tested until you're transferred to primenet, where it is correct.

[QUOTE=LaurV;328249]Already visible, the first ~2000 done (first 3 levels seems to be completed, 1+10+100+1000=1111 movies already). The 332M (on the level 4) is not done yet.[/QUOTE]

Actually, the first three levels, plus the forth for 30-70, and 330-340. So your campaign in 332M is now in [URL="http://www.mersenne.info/trial_factored_bar_graph_video/3/332000000/"]glorious technicolor[/URL]. :smile:

[QUOTE=Bdot;328288]There seems to be something odd with the underlying data (lying data?): [URL="http://www.mersenne.info/exponent_status_line_graph/2/30000000/"]30M.[/URL] Drilling down also shows the exponents not even first-time-tested until you're transferred to primenet, where it is correct.[/QUOTE]

Yeah... Sorry about that (and thanks for bringing it to my attention (again! :smile:)).

"Spidy" got some bad data from Primenet a while ago which slipped through its sanity checks somehow. I need to climb into the DB and fix that.

[QUOTE=chalsall;328321]Actually, the first three levels, plus the forth for 30-70, and 330-340. So your campaign in 332M is now in [URL="http://www.mersenne.info/trial_factored_bar_graph_video/3/332000000/"]glorious technicolor[/URL]. :smile:[/QUOTE]
Nice. Thanks! I took 200 more LLTF (61M) expos from GPU72 and put them into my worktodo list (actually at the beginning of it) to celebrate this! :smile:

[QUOTE=LaurV;328329]I took 200 more LLTF (61M) expos from GPU72 and put them into my worktodo list (actually at the beginning of it) to celebrate this! :smile:[/QUOTE]

Thanks a lot! We really need to get back to Primenet some more candidates. We're currently about 30 days ahead of the "wave", but it appears many more assignments than normal are being handed out by Primenet since the "big news". :smile:

[QUOTE=chalsall;328330]... many more assignments than normal are being handed out by Primenet since the "big news". :smile:[/QUOTE]
I trimmed my lltf from 75 to 74 bits for the sake of speed just in case we get overtaken in the 59M block.

[QUOTE=bcp19;328111]12 factors in one day :) 8 - 33M and 4 - 61M out of 300 tested exponents. I think I hit the jackpot![/QUOTE]

"I don't know. It must have been the roses." -GD (or the moon, or Mercury, or something.....)

On Feb. 6 I pulled down 3 factors out of 43 tested. All mid-61M, 25 71-73, 18 72- 73 (one of the factors in the latter group.)

I had to study a bit to get the numbers right. By GPU72's clock the factors landed at ~00:45 on the 7th, which, of course is still in progress here at -6 UTC. However, by my local time that is 18:45. My other LLTF upload on the 6th was at ~14:45 UTC, or 08:45 CST (US).

Figuring by percentages then[INDENT]Jerry = 2.667%
Kieren = 6.977% (:max:)
Both = 3.207% factors
[/INDENT]I wonder if anyone else hit the jackpot on the 6th, or what the factor percentage for GPU72 was compared to the long-term average.

[QUOTE=kladner;328346]]I wonder if anyone else hit the jackpot on the 6th, or what the factor percentage for GPU72 was compared to the long-term average.[/QUOTE]

Yesterday was a very good, but not an exceptional, day. Please see [URL="https://www.gpu72.com/graphs/factors/month/"]this graph[/URL].

Note that because of GPU72's temporal spreading algorithm, most of the factors reported on the 6th are shown as the 5th here. As in, the candidates for which factors were found were assigned on the 5th or earlier.

The Linear Regression Trend line is the most important to follow.

Thanks! I see what you mean. The upward trend is good to see. Also, 1/31 was even better, especially in P-1.

since time flies at my age...
 

If I look at this report:

[url]http://www.gpu72.com/reports/estimated_completion/primenet/[/url]

It suggests that by the end of 2013 all the required DC-TF to 50M and (by my extrapolation) all the LL-TF to 70M as well will be complete

Then what?

I'm sure neither wave will be anywhere those limits by then.

[QUOTE=petrw1;328385]If I look at this report:

[URL]http://www.gpu72.com/reports/estimated_completion/primenet/[/URL]

It suggests that by the end of 2013 all the required DC-TF to 50M and (by my extrapolation) all the LL-TF to 70M as well will be complete

Then what?

I'm sure neither wave will be anywhere those limits by then.[/QUOTE]

Redirect to LL testing? LMH factoring? Will P-1 also be caught up at that point?

[QUOTE=petrw1;328385]by the end of 2013 all the required DC-TF to 50M and (by my extrapolation) all the LL-TF to 70M as well will be complete[/QUOTE]

Your link is broken. Anyway, the ETAs are of the "if everyone does only this" type.

Since DCTF only gets around 1/7th of GPU72's TF power, at least on that front we are save for a few years. We'll probably try and close the gap to the LLTF tail afterwards.

As far as LLTF goes, we'll probably simply go higher, or deeper, or both.

Am I correct in assuming that once the DC wave is where the LLTF wave began, there will be no more DCTF?

[QUOTE=c10ck3r;328405]Am I correct in assuming that once the DC wave is where the LLTF wave began, there will be no more DCTF?[/QUOTE]

Mostly, yes.

[QUOTE=c10ck3r;328405]Am I correct in assuming that once the DC wave is where the LLTF wave began, there will be no more DCTF?[/QUOTE]

I think there will always be a Double Check TF wave... it just goes up, unless they all get factored before first LL... which probably will happen.

[QUOTE=kracker;328411]I think there will always be a Double Check TF wave... it just goes up, unless they all get factored before first LL... which probably will happen.[/QUOTE]

No.

Because a DC candidate only needs about one "bit" less of TFing than a LL candidate in about three years or so there will be no DCTF left to do.

[QUOTE=chalsall;328415]No.

Because a DC candidate only needs about one "bit" less of TFing than a LL candidate in about three years or so there will be no DCTF left to do.[/QUOTE]

Ok, I see what you mean. :smile:

[QUOTE=ckdo;328398]Your link is broken. Anyway, the ETAs are of the "if everyone does only this" type.
[/QUOTE]

Ah, missed that one little factoid...I assumed (yeah, I know) he was basing it on progress for each work type

FWIW, I think if we are trusting James' latest chart, the 'go deeper' bit will happen before we complete the current set. I am not sure what that graph calculates 'complete' as, (72 bits for 60m range? 73?) but that last graph from James shows the 60M range break even point at > 74, so I figure at some point the 'Estimated Days' graph will be recalibrated. I will be surprised if it takes 3 years to do so.

As an aside, this is the first time I've seen someone mention about the DC ending. I had looked into that some time ago and while I wasn't 100% on at exactly which M range it would end on (I was guessing 56) it did seem certain it would end. I simply couldn't calc how long that would take. It is good to have that knowledge in the public forum.

[QUOTE=Aramis Wyler;328598]FWIW, I think if we are trusting James' latest chart, the 'go deeper' bit will happen before we complete the current set. I am not sure what that graph calculates 'complete' as, (72 bits for 60m range? 73?) but that last graph from James shows the 60M range break even point at > 64, so I figure at some point the 'Estimated Days' graph will be recalibrated. I will be surprised if it takes 3 years to do so.[/QUOTE]

All true. But please keep in mind that even before the "big news" we were only just keeping ahead (and slowly building a buffer in front) of the LL "wave" only going to 73, rather than the 74 where we should have been.

I'm monitoring the assignments being issued by Primenet currently, but there's a chance we'll have to start releasing candidates at only 72 for a while. If that happens, we'll still have about an 80% chance of having another opporutnity to bring them back in for processing to 73 after the post-news "surge" finishes. Only about 20% of all LL assignments actually complete, and that will probably be even lower for what is being assigned at the moment.

I like that this is a fluid and carefully monitored thing.

I think it would be better if we had a defined target and a defined calulation for how close we were going to attempt to get to target (eg, if the target for 60M is 74 bits, we would relase it at 72 (target-2) if we were < 2 weeks ahead of the wave, or 73 (Target-1) if we were only 1 month ahead of the wave, and would keep it till 74 if we were > 30 days head.

These timespans are arbitrary that I'm making up - it's just to describe the concept of the formula I'm discussing, which in this case would be [Release Bit Depth] = [Target Bit Depth] - trunc([Lead Weeks]/2) where leadweeks < 5.

The point is, I understand that's a bit simplistic and so am glad it's actually monitored by a person with judgement.

ALSO: I think it would be pretty cool to have like, a DEFCON 2 OR DEFCON 1 theme on the page if our leadtime was low enough that we were reducing our release point by necesity. :w00t:
ALSO ALSO: If I get my old card running in parallell with my new card I'll set the old one to do a bitdepth of just 73. My current one is (currently) on 74.

[QUOTE=Aramis Wyler;328604]ALSO: I think it would be pretty cool to have like, a DEFCON 2 OR DEFCON 1 theme on the page if our leadtime was low enough that we were reducing our release point by necesity. :w00t:[/QUOTE]

LOL... In that case, ALL HANDS ON DECK!!! WE'RE CURRENTLY AT DEFCON 1!!! :wink:

[QUOTE=Aramis Wyler;328604]ALSO ALSO: If I get my old card running in parallell with my new card I'll set the old one to do a bitdepth of just 73. My current one is (currently) on 74.[/QUOTE]

Cool, Thanks.

Every cycle available from everyone could really be used at LLTFing right now, even if it's only going from 70 -> 71. I'm going to move my 560 to LLTFing as well (when it finishes its current "real-work" assignment).

[QUOTE=chalsall;328609]LOL... In that case, ALL HANDS ON DECK!!! WE'RE CURRENTLY AT DEFCON 1!!! :wink:

Every cycle available from everyone could really be used at LLTFing right now, even if it's only going from 70 -> 71. I'm going to move my 560 to LLTFing as well (when it finishes its current "real-work" assignment).[/QUOTE]

That being the case, let me say that I have some DCTF in queue, but not started. I would be glad to throw them back into the GPU72 pool and let MISFIT fetch only LLTF.

EDIT: What say you, Captain Halsall?

[QUOTE=kladner;328613]EDIT: What say you, Captain Halsall?[/QUOTE]

LOL... As always, people are free to do whatever they want. However, it would be best for GIMPS overall if all cycles went to LLTFing for at least the next month.

As Admiral Woltman himself signed off on, even if a few 32Ms (already at 70 "bits") are assigned before we eventually take all of 31M to 70, it won't be a long-term detriment to the project.

Aye aye, Sir!

Yup we need LLTF on GPUs and P-1 on CPUs. I'm currently suspending DCs and doing P-1 on all four cores of my home rog now that I got extra memory last week.

The range of 65M - 66M seems to be locked...
could anybody verify this?

[QUOTE=Redarm;328678]The range of 65M - 66M seems to be locked...
could anybody verify this?[/QUOTE]

Not "locked", simply that we don't have any candidates available there at the moment.

Please see the [URL="https://www.gpu72.com/reports/available/"]Available Assignments[/URL] report to see what's available. Choosing "What Makes Sense" (with the ranges left as default) on the assignments form will always have assignments available (as shown in the preview area).

It's funny someone would bring that up. I was thinking last night that the 'exponent range' you could request (for lltf, at >71 bitdepth) was 0 to 100000000 but really no matter how you fiddled with the numbers you weren't going to get anything outside of 60-65M with tf of 71-73, and could only creep into 59M at 74+.

I especially love the warning for if you set the bitdepth to 71 - Only numbers above 60M!!! - which is, of course, the same as 72 or 73. :smile:

No complaints here, but I am curious about something. How come when we watch the factoring graph movies (love those things! Thanks for updating!) the 50-53M range only appears to be about half factored. Is there a reason those aren't made available to factor? I'm not sure they should be considered double checks since I'm currently doing first time tests on 6 LLs and 5 of them are < 54M (The other is 54M).

[QUOTE=Aramis Wyler;328681]It's funny someone would bring that up. I was thinking last night that the 'exponent range' you could request (for lltf, at >71 bitdepth) was 0 to 100000000 but really no matter how you fiddled with the numbers you weren't going to get anything outside of 60-65M with tf of 71-73, and could only creep into 59M at 74+.[/QUOTE]

Yes. GPU72 only "brings in" (read: officially reserves from Primenet) a few tens of thousands of candidates at a time for "lending" to GPU72 participants.

[QUOTE=Aramis Wyler;328681]I especially love the warning for if you set the bitdepth to 71 - Only numbers above 60M!!! - which is, of course, the same as 72 or 73. :smile:[/QUOTE]

Thanks for reminding me -- that's legacy code from when we still had work to do below 60M, and I didn't want people wasting everyone's time by only going a step-at-a-time there.

[QUOTE=Aramis Wyler;328681]No complaints here, but I am curious about something. How come when we watch the factoring graph movies (love those things! Thanks for updating!) the 50-53M range only appears to be about half factored. Is there a reason those aren't made available to factor? I'm not sure they should be considered double checks since I'm currently doing first time tests on 6 LLs and 5 of them are < 54M (The other is 54M).[/QUOTE]

The graphs, charts, movies etc (which are unfortunately temporarily off-line; the server hosting that appeared to have suffered a DDOS last night (my provider, 1and1, are working on it)) don't differentiate between LL and DC for the factor-level.

However, the [URL="https://www.gpu72.com/reports/estimated_completion/primenet/"]GPU72 Esitmated Completion[/URL] report does, and I can assure you that everything which is still an LL candidate below 57M is at at least 72, and everything between 57M and 60M is at at least 73.

Ah, so those remnants in the 50-53M range have actually been factored - by a LL test - but the chart is only showing the ones that were factored by trial factoring, ecm, and p-1?

[QUOTE=Aramis Wyler;328690]Ah, so those remnants in the 50-53M range have actually been factored - by a LL test ...[/QUOTE]

You got the nomenclature slightly wrong... They weren't "factored" by an LL test, but instead had a successful (read: no errors) LL test (which can't find factors). Thus they are now classified as Double Check (DC) candidates.

DC candidates deserve approximately one less level of TFing since a factor found will only save approximately one test (the DC), instead of approximately two (the LL and then the DC).

[QUOTE=Aramis Wyler;328690]... but the chart is only showing the ones that were factored by trial factoring, ecm, and p-1?[/QUOTE]

The chart is showing the trial factoring level for [B][I][U]all[/U][/I][/B] candidates, LL, DC and "cleared" (read: have had a successful LL and a matching DC proving them composite).

Note that for finding factors only TFing is "deterministic" and can be represented with a single simple integer. P-1 and ECM use very different techniques, and currently their statistics are not "visualized".

primenet denies TF-assignments in that range (65M - 66M) too, don't understand why :(

[QUOTE=Redarm;328697]primenet denies TF-assignments in that range (65M - 66M) too, don't understand why :([/QUOTE]

I don't know for a fact, but it's possible George is keeping the 60M to 70M range for GPU72 to manage.

We [B][I][U]really[/U][/I][/B] need to focus on the lower 60s ranges right now (you'll see why shortly), but if you [I][U]really[/U][/I] want to work in 65M, I'll bring some in for you.

[QUOTE=chalsall;328609]ALL HANDS ON DECK!!! WE'RE CURRENTLY AT DEFCON 1!!![/QUOTE]

Is there a DEFCON 0??? :wink:

Before the big announcement Primenet was only handing out about 183 candidates a day (taking into account the expires which get recycled). At that rate we had about a 30 day lead, and were very slowing gaining (going to 73).

The number of LL assignments being issued by Primenet is now around 1,000 a day!!!

Therefor, I have temporarily lowered the default TF level for LL from 73 to 72, in preparation for having to start releasing at that level. I've also lowered the number of candidates at 73 cached for P-1 work, and will continue to lower this number as the need arises.

We still have about a three day lead, but unless we can produce about 1,000 TF results to at least 72 a day, we're toast!

Also, it would be helpful if those who are doing P-1 work would complete and return them to Primenet as soon as possible.

GPU72.com out.... :wink:

[QUOTE=chalsall;328699]We [B][I][U]really[/U][/I][/B] need to focus on the lower 60s ranges right now [/QUOTE]

Affirmative!

Chris,

Do you want me to un-reserve everything and re-reserve with pledge to 72? I can turn a lot more up to 72 than I'm doing to 73.

I'm stopping my 100 assignment DC work.
 

Reconfiguring fetching to 72.

Did I mention I am actually on the GPU72 team now..... Must comply with the boss!

[QUOTE=flashjh;328714]Do you want me to un-reserve everything and re-reserve with pledge to 72? I can turn a lot more up to 72 than I'm doing to 73.[/QUOTE]

If that's not too much of a pain for you, but would be really useful.

In my mind there is now no question that we're going to have to start releasing at 72 again for at least a while.

I had hoped that the "surge" would only last for a few days, but the press coverage has been very successful, and the downloads I'm seeing for the Prime95 / mprime clients from my mirror are only increasing at the moment....

[QUOTE=swl551;328717]Reconfiguring fetching to 72.

Did I mention I am actually on the GPU72 team now..... Must comply with the boss![/QUOTE]

Thanks for the reconfiguration, and for joining the Primenet GPU72 team!

And I'm not the boss (I know you were joking), George is. I'm just a facilitator who happens to have access to a great deal of real-time information which I bring to everyone's attention when appropriate.

[QUOTE=chalsall;328718]If that's not too much of a pain for you, but would be really useful.[/QUOTE]

All done. I have 6 left to 73 that were already in progress and then everything else is 72. It will take MISFIT a couple of hours to populate my work files, but I picked up 100 for now.

Quick education...
 

What program works on work type of P-1 Factor

Prime95

[QUOTE=flashjh;328721]All done. I have 6 left to 73 that were already in progress and then everything else is 72. It will take MISFIT a couple of hours to populate my work files, but I picked up 100 for now.[/QUOTE]

Coolness! Thanks.

If all of our firepower moves from going to 73 to instead go to 72, we should be good. This surge can't last forever! (Can it? :wink:)

Also, as I mentioned earlier, we'll probably have something like a 80% chance to bring each candidate back in for appropriate processing (or, at least, to 73...) in a couple of months.

[QUOTE=flashjh;328721]All done. I have 6 left to 73 that were already in progress and then everything else is 72. It will take MISFIT a couple of hours to populate my work files, but I picked up 100 for now.[/QUOTE]
Flash,
Don't forget you can click the "Add Work" button and execute push-button fetches to load up faster.

[QUOTE=chalsall;328703]Is there a DEFCON 0??? :wink:

Before the big announcement Primenet was only handing out about 183 candidates a day (taking into account the expires which get recycled). At that rate we had about a 30 day lead, and were very slowing gaining (going to 73).

The number of LL assignments being issued by Primenet is now around 1,000 a day!!!

Therefor, I have temporarily lowered the default TF level for LL from 73 to 72, in preparation for having to start releasing at that level. I've also lowered the number of candidates at 73 cached for P-1 work, and will continue to lower this number as the need arises.

We still have about a three day lead, but unless we can produce about 1,000 TF results to at least 72 a day, we're toast!

Also, it would be helpful if those who are doing P-1 work would complete and return them to Primenet as soon as possible.

GPU72.com out.... :wink:[/QUOTE]
Chris, I am sure the announcement has brought in lots of new participates but I'm wondering if you how much mfaktc 0.20 increased the number of CPUs that started to run p95. I went from 0 p95 threads to 23 threads once all my equipment was converted to 0.20.

thx

[QUOTE=swl551;328729]Chris, I am sure the announcement has brought in lots of new participates but I'm wondering if you how much mfaktc 0.20 increased the number of CPUs that started to run p95. I went from 0 p95 threads to 23 threads once all my equipment was converted to 0.20.[/QUOTE]

The assignment surge correlates perfectly with the "new prime" news coverage. It correlates very (very) lightly with mfaktc 0.20 -- well below statistical significance.

Not at all to take away from Oliver's, George's and rcv's amazing and significant work on 0.20, but the surge we're seeing is because of the new prime.

Also, please keep in mind, I [I]think[/I] (do not know) that many who suddenly found themselves with spare CPU capacity started doing P-1. I know I did.

[QUOTE=chalsall;328703]Is there a DEFCON 0???
[/QUOTE]

[url]http://en.wikipedia.org/wiki/DEFCON[/url]

not according to this you basically just called for nuclear war.

[QUOTE=flashjh;328721]All done. I have 6 left to 73 that were already in progress and then everything else is 72.....[/QUOTE]

I'll make the change when I have a chance to go through everything. Have guests right now. :smile:

[QUOTE=science_man_88;328736][url]http://en.wikipedia.org/wiki/DEFCON[/url]

not according to this you basically just called for nuclear war.[/QUOTE]

Sigh.... You are such an idiot...

I'm sorry you are from the same area my favorite comedians are from...

I unqueued all my 74bit work from the 59M range and reconfigured fetch to do 72bit work. I hope it will not stay that way for long though. I think I an chuck out about 55 a day at 72.

[QUOTE=Aramis Wyler;328739]I unqueued all my 74bit work from the 59M range and reconfigured fetch to do 72bit work. I hope it will not stay that way for long though. I think I an chuck out about 55 a day at 72.[/QUOTE]

Thanks Aramis.

The "incoming" will probably be only for a short while.

But as we all know the battle cry: "Better to LL at 72 than 71". :wink:

[QUOTE=swl551;328726]Flash,
Don't forget you can click the "Add Work" button and execute push-button fetches to load up faster.[/QUOTE]
I still owed you a test from when you updated MISFIT. I wanted to make sure it would do everything on its own. I proud to report that it's working great!

Also, nice touch to your MISFIT directory online:

[CODE][URL="http://www.mersenneforum.org/misfit/downloads/if_i_die/"]if_i_die/[/URL][URL="http://www.mersenneforum.org/misfit/downloads/if_i_die/"]
[/URL][/CODE]
:smile:

[QUOTE=chalsall;328731]The assignment surge correlates perfectly with the "new prime" news coverage.[/QUOTE]Have seen a bump up of ~1/3 increase in the number of 332M LL assigned expos. We were running around 1500 for quite a while. Now it is 2200. I hope that they all do TF to at least 77 first.

OK I just returned all the "to 73" work and reloaded with "to 72".

got the 480 running in parallell with the 580. Both set to 72. Should be about 105/day.

Hehe Chris. I told you so :razz: I am glad you are keeping such a close watch on things and that there is such a responsive crowd here.

I released about 20 LLTF exponents to 73 and got some assignments to 72; finishing my P-1 exponents that are already at 73.

Luigi

Both GPUs cleared out and reloaded with 71-72s here. They should do a little less than 82/day.

[QUOTE=Redarm;328697]primenet denies TF-assignments in that range (65M - 66M) too, don't understand why :([/QUOTE]

[QUOTE=chalsall;328699]I don't know for a fact, but it's possible George is keeping the 60M to 70M range for GPU72 to manage.[/QUOTE]

That would be way too complicate. I think is a consequence of the fact that according with PrimeNet/Prime95 criteria (which is not GPU-aware), some ranges are already TF-ed too much. Indeed CPU-TF of 60M range to 73-74 bits would be somehow insane...

[QUOTE=kladner;328802]Both GPUs cleared out and reloaded with 71-72s here. They should do a little less than 82/day.[/QUOTE]

Thanks everyone for your speedy response! :smile:

[QUOTE=garo;328788]Hehe Chris. I told you so :razz:[/QUOTE]

Yeah, I know... And I did listen to you, but I didn't appreciate just how much of a "surge" you meant... :blush:

[QUOTE=garo;328788]I am glad you are keeping such a close watch on things and that there is such a responsive crowd here.[/QUOTE]

Indeed. We've got a good team effort here! Thanks again everyone! :smile:

[QUOTE=chalsall;328827]Yeah, I know... And I did listen to you, but I didn't appreciate just how much of a "surge" you meant... :blush:
[/QUOTE]

I've seen a bunch of these dang things discovered and seen what happens to the server. I think the last couple of discoveries had muted responses because they came so close after the 10 million digit find and mass media can only handle so many record primes a decade :smile: After 4+ years I felt there would be a pent-up demand.

PS: Book off to publisher.

Lowering alert level to DEFCON 2.
 

Just a status update for everyone...

The surge appears to be abating... "Only" ~800 assignments were issued yesterday.

Also, at the suggestion of Garo and the approval of George, I have brought in every available candidate below 64M TFed to less than 73 "bits". Thus there are approximately 6,534 candidates at 73 bits or above which can be issued by Primenet for LLing or P-1'ing.

If all of those are issued (unlikely), we have ~2,500 (and climbing) candidates at 72 bits ready to release back to Primenet.

So, basically what I'm saying is it now doesn't appear we're going to have to release at 72 after all, even though we're ready to do so if needed.

My apologies for causing everyone to do the big change to 72 bits on Saturday, but for a while there it looked like we were about to be swamped. I'm going to leave the default settings at 72 for at least another day to make sure we've got a few more days of lead time, then I'll move it back up to 73.

Also, all MISFIT users should see [URL="http://www.mersenneforum.org/showthread.php?p=328878#post328878"]this discussion[/URL]. I'm going to implement a change for the "What Makes Sense" option such that the system will make the decision as to what the Pledge level should be. But, to be clear, this is only for MISFIT users; manual (read: human) use will remain the same.

Specifically, the impact to MISFIT users is if you only want to go to 72 (or 71) you should change the "Option" setting from WMS to "Lowest Exponent" or "Lowest TF Level", etc. Only the WMS option will override the Pledge and Range settings. Lastly, WMS will never change the worktype; LLTF requests will always be LLTF, ditto for DCTF.

Thanks for the cycles everyone! :smile:

@chalsall I guess we really do [URL="http://mersenneforum.org/showthread.php?p=328969"]need more[/URL] P-1... :unsure:

[QUOTE=kracker;328983]@chalsall I guess we really do [URL="http://mersenneforum.org/showthread.php?p=328969"]need more[/URL] P-1... :unsure:[/QUOTE]

Definitely. But there's little chance of that happening in time.

Even before the "surge" approximately 25% of all assignments were without P-1. Now it's up to something like 90%.

We're given' all she's got, Captain! The dilithium crystals canna tak nae mair! :max:

[QUOTE=kladner;328994]We're given' all she's got, Captain! The dilithium crystals canna tak nae mair! :max:[/QUOTE]

ROFLMAO...

We do what we can. 8-)

[QUOTE=chalsall;328985]Definitely. But there's little chance of that happening in time.

Even before the "surge" approximately 25% of all assignments were without P-1. Now it's up to something like 90%.[/QUOTE]

On the bright side, some new participants may complete P-1 testing before doing the LL, so even if they get discouraged and don't finish the LL, at least they will have made a small contribution. It will be interesting to see what percentage of the new volunteers have reported progress within 60 days.

:razz:
Maybe I might consider switching some of my DC [strike]machines[/strike] minions to P-1.

[QUOTE=kracker;329006]:razz:
Maybe I might consider switching some of my DC [strike]machines[/strike] minions to P-1.[/QUOTE]

You definitely should. I have converted 5 cores from DC to P-1.

[QUOTE=garo;329024]You definitely should. I have converted 5 cores from DC to P-1.[/QUOTE]

I will. :smile: Most of the [strike]machines[/strike] minions don't have enough memory, but I think I have 12 cores that have enough, the rest of them... nope... at least not now, that's why they're doing DC. :smile:

[QUOTE]Most of the [strike]machines[/strike] minions don't have enough memory…[/QUOTE]You might be surprised how little memory you can use and still get good results:

[url]http://www.mersenneforum.org/showpost.php?p=282335&postcount=10[/url]

Plus, you can use "MaxHighMemWorkers" to help.

:spot:

[QUOTE=Xyzzy;329035]You might be surprised how little memory you can use and still get good results:

[URL]http://www.mersenneforum.org/showpost.php?p=282335&postcount=10[/URL]

Plus, you can use "MaxHighMemWorkers" to help.

:spot:[/QUOTE]

Thanks doggie! :smile:

On another note, gpu72 appears down.

[QUOTE=kracker;329037]On another note, gpu72 appears down.[/QUOTE]

Interesting... We appear to be under subtle attack....

Edit: From Germany no less. 81.30.156.103.