S5R2

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4,240
Credit: 244,323,199
RAC: 23,938

sorry Mike, always nice to

sorry Mike, always nice to chat with you, I hope we'll pick up later. some bugs will eat me here if I don't kill them now...

BM

BM

J Langley
J Langley
Joined: 30 Dec 05
Posts: 50
Credit: 58,338
RAC: 0

RE: I'm not that much into

Message 62091 in response to message 62088

Quote:
I'm not that much into assembler-programming yet, it's a bit too early (also I will try again to take more advantage of auto-vectorization this time, giving much more flexibility).
BM

I seem to remember that for the current run SSE2 and SSE3 didn't provide much of a performance boost over SSE. Will this still be the case for S5R2 and S5R3? And does the upcoming SSE4 look like it might provide any useful instructions?

Chilango
Chilango
Joined: 4 Jan 06
Posts: 2
Credit: 4,321,270
RAC: 0

RE: After sometime I

Message 62092 in response to message 62072

Quote:

After sometime I terminated the first unit with S5R2.
I need a long time, about 12 hours (51.900 sec). So I needed about 5,4 times
more than normal. So I am a little bit disapointed that I get only 113 points.
The double of the normal units.


Annika
Annika
Joined: 8 Aug 06
Posts: 720
Credit: 494,410
RAC: 0

Well, I haven't had any luck

Well, I haven't had any luck so far, only "S5RI" WUs... hope to finish them soon and try again ;-)

archae86
archae86
Joined: 6 Dec 05
Posts: 3,140
Credit: 6,964,231,598
RAC: 1,791,133

RE: After sometime I

Message 62094 in response to message 62092

Quote:
After sometime I terminated the first unit with S5R2.
I need a long time, about 12 hours (51.900 sec). So I needed about 5,4 times
more than normal. So I am a little bit disapointed that I get only 113 points.
The double of the normal units.

Wow, 41,873.89 CPU seconds for a Core 2 E6600 to finish one result. Looks like some long crunch times ahead. The bright spot is that will amortize the network traffic of the big downloads.

Svenie25
Svenie25
Joined: 21 Mar 05
Posts: 139
Credit: 2,436,862
RAC: 0

RE: Well, I haven't had any

Message 62095 in response to message 62093

Quote:
Well, I haven't had any luck so far, only "S5RI" WUs... hope to finish them soon and try again ;-)

Same here. I think, I will switch off the light at the S5RI. ;)

Quote:
Wow, 41,873.89 CPU seconds for a Core 2 E6600 to finish one result. Looks like some long crunch times ahead. The bright spot is that will amortize the network traffic of the big downloads.

And what about the credits for this monster of WU?

Annika
Annika
Joined: 8 Aug 06
Posts: 720
Credit: 494,410
RAC: 0

Archae, are you serious? That

Archae, are you serious? That will mean some gigantic crunching times on slower boxes... Luckily I've got two fast ones which should cope well. Maybe I'll switch the slower ones over to other projects and alter the resource shares on the racehorses a bit to make up for it.

Bruce Allen
Bruce Allen
Moderator
Joined: 15 Oct 04
Posts: 1,119
Credit: 172,127,663
RAC: 0

An update on our

An update on our progress:

(1) We fixed a problem with the validator where some results where erroneously being marked as validate errors. I re-ran the fixed validator on these results so credit was granted.

(2) I've done some preliminary analysis of credit granted and determined that we were not awarding enough credit. For all S5R2 workunits WITHOUT a valid result (at the moment, all but 52) I have fixed this in the database. Credit awarded for the S5R2 WU will now be larger by a factor of 2.222. Note that in the past Einstein@Home has been giving out 30% too much credit compared with other projects (see BOINC cross-project credit comparison for details). The factor of 2.222 takes this into account.

Further updates will follow.

Note: we are still in the process of rsyncing (mirroring) our new S5 data to the mirror download servers. So the first S5R2 workunits all reference the Einstein@Home server in Wisconsin as the data source.

Cheers,
Bruce

Director, Einstein@Home

archae86
archae86
Joined: 6 Dec 05
Posts: 3,140
Credit: 6,964,231,598
RAC: 1,791,133

RE: Archae, are you

Message 62098 in response to message 62096

Quote:
Archae, are you serious? That will mean some gigantic crunching times on slower boxes... Luckily I've got two fast ones which should cope well. Maybe I'll switch the slower ones over to other projects and alter the resource shares on the racehorses a bit to make up for it.

I'm just reading Chilango's results from the link to his id in message 66051.

Quote:
And what about the credits for this monster of WU?


Again relying on the results page for Chilango's one computer.

Eyeballing an average, it has recently been spending typically about 7400 CPU seconds to do an S5RIa result, getting 53.6 cobblestones. The single S5R2c turned in so far on that machine reported consuming 41,873.89 CPU seconds and is poised to receive 112.59 cobblestones. With two cores on the machine, that would be a drop from 52 cobblestones/hour to 19, before allowing for less than 100% usage, efficiency, etc.

It is but a single sample, and I may be misreading it, but, yes, it seems we shall be getting results which take much longer to compute, and our rate of cobblestones/hour looks set to drop by well over a factor of two. There might be something special about the E6600 here, but I actually think that unlikely.

[edit: this post was, I think, accurate at the time I wrote it--however it took some time before I was able to post it, by which time it was overtaken by Bruce Allen's post. If I understand correctly, the above-mentioned result would now be awarded 249.95 cobblestones, which would make the stock E6600 implied hourly rate something like 42 cobblestones/hour, not 19]

Richard Haselgrove
Richard Haselgrove
Joined: 10 Dec 05
Posts: 2,139
Credit: 2,707,457,780
RAC: 1,558,198

Thanks to Bernd & Bruce for

Thanks to Bernd & Bruce for the heads-up.

Is Chilango's result (the only one I've seen linked so far) likely to be typical in terms of production run-time - i.e. 5.4 times S5RI run-time, in his estimation? (I stress production run-time, since it looks as if it still has a lot of debug output).

If so, you might like to consider whether 14 days is still the appropriate deadline: my Celeron, allowing for its current 50% share with SETI, would take about 17 days pro-rata. Not that the project should be run for the benefit of one superannuated cruncher, of course!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.