As it has been said, his generic optimizations, and some extra optimizations have been put into the new application. Specific optimizations like SSE, SSE2, SSE3, etc. can not be pushed out, because currently the BOINC system does not relay that information back to the projects as to ask for that deep of an optimization.
The current (x86-) Apps do incorpoarate specific optimizations for SSE, they do detect the CPU they're running on and will choose to execute code for this specific CPU. However this distinction is currently only made between SSE and non-SSE CPUs. You will find a line in the stderr output of your results that reflects this: "Detected CPU type" - 1 means SSE, 0 means generic.
We (Akos and I) will continue to work on speeding up the Apps. This will probably include code for more CPU variants (3Dnow!, SSE3). Some things that are advantagous for one or the other CPU type may be hard to incorporate in an App that switches CPU types, e.g. instruction order and code alignment, such that the switching doesn't eat up all the speed gained, but I think there are quite some things left to try.
IMHO reporting a more detailed platform from the client to the project would lead to the possibility of distributing faster Apps. Some discussion about that has started on the BOINC devleopers mailing list, but that's quite a way to go until that would be implemented and can be benificial to the projects.
Akos isn't working exclusively for Einstein@Home and I have also been busy with preparing, implementing and testing the S5R1 setup, and will probably continue to be the next one or two weeks to iron out the last issues that arise. So the "science code" that determines the speed of the Apps is currently freezed.
The intention is that the average Einstein@Home participant will get the same credit per hour "work" than what he gets on other BOINC projects. However with the large variety of Platforms, Apps and Clients we currently have it requires quite some investigation and testing to find out the average participant configuration, or the "standard credit rate" which you mentioned.
Note, Seti_Enhanced-numbers was increased 4.776%, since next release will have roughly 5% higher credit-claims.
Appart for showing the 2nd. system has abysimal memory-bandwidth, not sure if can draw any other conclusions, appart for CPDN Coupled Model is too high even compared to Seasonal Attribution...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
It's true. Bruce has forced the old S4 WU generator to generate all the remaining S4 Tasks and put them into the database, so that it is not needed any longer and the WU generator for S5R1 could be properly set up.
I just checked my results, got 4 slices for the 15.47MB version and I am the only one who got 3 of them. For the other PC the results were unsent. I hope that in due time they get sent to others as well? Or I'll be waiting for the quorum of 2 for ages.
RE: As it has been said,
)
The current (x86-) Apps do incorpoarate specific optimizations for SSE, they do detect the CPU they're running on and will choose to execute code for this specific CPU. However this distinction is currently only made between SSE and non-SSE CPUs. You will find a line in the stderr output of your results that reflects this: "Detected CPU type" - 1 means SSE, 0 means generic.
We (Akos and I) will continue to work on speeding up the Apps. This will probably include code for more CPU variants (3Dnow!, SSE3). Some things that are advantagous for one or the other CPU type may be hard to incorporate in an App that switches CPU types, e.g. instruction order and code alignment, such that the switching doesn't eat up all the speed gained, but I think there are quite some things left to try.
IMHO reporting a more detailed platform from the client to the project would lead to the possibility of distributing faster Apps. Some discussion about that has started on the BOINC devleopers mailing list, but that's quite a way to go until that would be implemented and can be benificial to the projects.
Akos isn't working exclusively for Einstein@Home and I have also been busy with preparing, implementing and testing the S5R1 setup, and will probably continue to be the next one or two weeks to iron out the last issues that arise. So the "science code" that determines the speed of the Apps is currently freezed.
BM
BM
RE: The intention is that
)
Well, for that it's worth...
Granted credit/hour:
cpu - Einstein/S5 - Predictor - Seti_Enh. - BBC/CPDN - Seasonal
Opt.242 - 9.38 CS/h - 9.93 CS/h - 8.28 CS/h - 10.76 CS/h - 8.26 CS/h
MP2400+ - 11.87 CS/h - 9.33 CS/h - 6.50 CS/h - 6.81 CS/h
Note, Seti_Enhanced-numbers was increased 4.776%, since next release will have roughly 5% higher credit-claims.
Appart for showing the 2nd. system has abysimal memory-bandwidth, not sure if can draw any other conclusions, appart for CPDN Coupled Model is too high even compared to Seasonal Attribution...
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
S4 generator just runned out
)
S4 generator just runned out of work! Woo hoo.
RE: S4 generator just
)
I wonder if they turned up the speed of making the WUs just to get them done, so S5 testing, etc. can move on?
RE: RE: S4 generator just
)
That's likely, status page reports 224,597 unsent results instead of usual 10,000 ...
It's true. Bruce has forced
)
It's true. Bruce has forced the old S4 WU generator to generate all the remaining S4 Tasks and put them into the database, so that it is not needed any longer and the WU generator for S5R1 could be properly set up.
BM
BM
I just checked my results,
)
I just checked my results, got 4 slices for the 15.47MB version and I am the only one who got 3 of them. For the other PC the results were unsent. I hope that in due time they get sent to others as well? Or I'll be waiting for the quorum of 2 for ages.
S5 progress box just appeared
)
S5 progress box just appeared on the Status page.
16,446,454 units. Ouhh, that's a lot of work.
I just finish my first S5
)
I just finish my first S5 unit, claimed credit 119, for 13h00 of work.
http://einsteinathome.org/workunit/9763626
RE: I just finish my first
)
Oh my god... 13 hours of work?
I'll need to overclock more my computer =( hahahaha...
Regards,