RSA Lattice Server moving to NFS@Home and shutting down

[Fire$torm]

@somanyroads: Nope this is as good a place as any since it is related. As to an answer? Sorry but I haven't a clue.

@Everyone:

This is a friendly admin notice. I am sending out the team mass email for the Sept. SIMAP challenge and included a call to arms for the RSA project. Hopefully we should see additional members on this project soon.

F$

[DrPop]

Somebody talk to me here...I just got the email and will check back in the morning. Should I move the hydra heads over to this lattice? I see someone made a Hydra account there so I'll do it if you think we have a shot for the team.
@Trigggl - my man, throw that hydra head on your own account and make a run for 100K! Never know until you try and I know you want the 100K in the end...

Sent from my MB860 using Tapatalk 2

[Mike029]

Maybe this is the wrong place . . . . but why does an 8 core Intel i7 on 7.0.28 have half the RSA Lattice Seiver cpu output of a 6 core AMD on 6.10.34? Both machines started work at the same time. I had to remove 7.0.28 from another machine and reinstall 6.10.34 because RSA Lattice Seiver had locked up for 24 hours. GPUGRID seems to only run on the GTX 670 using 7.0.28.

Attachment 1078
If this is the wrong place for this question, I assume someone will move it to a more appropriate location. Sorry.

Hmm, not sure. I can't check my own six core vs I7 as RSA does not tell us anything about past wus once they are turned in.


@DrPop, I DO think we have a real shot at top spot. I say go for it.

[Mad Matt]

There are other projects like ECM@yoyo showing affinity for AMD. This can easily sum up to a nice difference. Anyhow, will make my tiny cores look even more pale.

http://wuprop.boinc-af.org/results/p...Lattice+Siever

[Mad Matt]

No clue why this is, but I am just having one rig validating more or less safely. Another validated 3 out of 20, the 2600k finally did not validate at all. Since I am at safe clocks, my guess is some interference with OpenCL...

So I am down to two cores atm. Sorry guys. Hope you got more luck.

[Duke of Buckingham]

I had problems validating and made a reset and have all fixed now.

[trigggl]

No clue why this is, but I am just having one rig validating more or less safely. Another validated 3 out of 20, the 2600k finally did not validate at all. Since I am at safe clocks, my guess is some interference with OpenCL...

So I am down to two cores atm. Sorry guys. Hope you got more luck.

Don't know why, but my Hydra head hasn't validated anything recently. I don't think it's an OpenCL problem. One of my boxes is validating just fine while also running Poem. Maybe it's specific task groups? I'm testing that theory right now by suspending all tasks from failing task groups. It's hard to know what's validating successfully, since they don't bother to keep the validated records beyond a couple minutes.

[Slicker]

Maybe this is the wrong place . . . . but why does an 8 core Intel i7 on 7.0.28 have half the RSA Lattice Seiver cpu output of a 6 core AMD on 6.10.34? Both machines started work at the same time. I had to remove 7.0.28 from another machine and reinstall 6.10.34 because RSA Lattice Seiver had locked up for 24 hours. GPUGRID seems to only run on the GTX 670 using 7.0.28.

I have a 24 core AMD and a 24 core Xeon. They are similar speeds and are within 1% of each other in credit on DistrRTgen. Both joined RSA at the same time a couple days ago but the Xeon has 33.9% MORE credit than the AMD server. That's just the opposite. Maybe it is just creditnew messing with everything.

[Mike029]

I just aborted everything I had and will see if that fixed the problem.

We will pass the French tonight and move into 3rd. 36 hours after that we should be in 2nd with about 5 to 8 days to take number one. More machines the faster we do this.

[Mike029]

Worked like a charm. All are validating as it should. No more errors.