I visited the message boards yesterday for the first time in a few months and was intrigued to see that there was an optimised client for Einstein. After reading through the various threads I replaced the standard Albert4.37 app with S39L on a P4 Prescott @ 3.2Ghz. Processing times have dropped from an average of 30k secs/wu to about 6.5k secs/wu. Some of the newer ones have been validated already so all looks well. Amazing indeed!
I visited the message boards yesterday for the first time in a few months and was intrigued to see that there was an optimised client for Einstein. After reading through the various threads I replaced the standard Albert4.37 app with S39L on a P4 Prescott @ 3.2Ghz. Processing times have dropped from an average of 30k secs/wu to about 6.5k secs/wu. Some of the newer ones have been validated already so all looks well. Amazing indeed!
And this should be strong encouragement to read the msg boards more often; you never know what transpires and how it effects you.
From your post on the SETI forums about donations... I do not think you are willing to help either. >:(
To me there is no difference between people who own some green badge and people who don't. Everybody contributes in a way of their ability. Period.
And if you feel comfortable by minusing, well, have fun. [/way off topic]
I visited the message boards yesterday for the first time in a few months and was intrigued to see that there was an optimised client for Einstein. After reading through the various threads I replaced the standard Albert4.37 app with S39L on a P4 Prescott @ 3.2Ghz. Processing times have dropped from an average of 30k secs/wu to about 6.5k secs/wu. Some of the newer ones have been validated already so all looks well. Amazing indeed!
1) Did you (also) take a closer look at LHC@H regarding optimization?
2) When will there be a SSE2 E@H app.?
1, Not yet.
2, I don't know. SSE2 would be good for a 1-2% faster code. :-)
Unfortunately, they won't allow you to. I posted the question two weeks ago on L@H crunchers corner. Considering tremendous amount of data that LHC will produce this is the right time to consider ways to make processing effective.
The answer was that the program is written in Fortran and that it would be difficult to make any comparison between their official and an optimised version.
Actually, just now I came to the idea that they didn't understand my question. I was not interested in optimizing L@H (as they probably understood) but in new application that must come to process data from Collider. L@H has a limited lifetime but the application I have in mind would/ will be a real challenge.
I visited the message boards yesterday for the first time in a few months and was intrigued to see that there was an optimised client for Einstein. After reading through the various threads I replaced the standard Albert4.37 app with S39L on a P4 Prescott @ 3.2Ghz. Processing times have dropped from an average of 30k secs/wu to about 6.5k secs/wu. Some of the newer ones have been validated already so all looks well. Amazing indeed!
Yes, you're Prescott will love 39L :)
For clarity I should say that since its a HT processor thats 2 wu's every 6.5k secs , so a real average would be 3.25k secs/wu.
If I was one of the developers of Einstein I'm not sure if I would be pleased about this development or embarrassed. From other posts it seems that this client will be adopted as the official one so it must be more of the former and not the latter. Kudos to the Einstein team.
On a related note is BOINC capable of distributing different version of the science app based on the client cpu type?
00109404: 8B 4C DE 80 83 EB 10 75 F3 89 EA 90 ->
00109404: 0F 18 44 DE 80 83 EB 10 75 F2 89 EA SETI_K78b
Ok, it seems I returned too late to download this update so I applied patch by hands. Patched version finished current WU successfully but all others finished with error immediately. So this version is not for Athlon XP.
Quote:
Well, I modified, but I'm not interested in SETI.
Very sad news for SETI crunchers :( Your SETI_K78 outperforms both Crunch3r's SSE2&3 versions on all Athlon 64/ Pentium 4 I have to install it.
It's amazing, thank you very much!
Maybe you would consider possibility of creation 3DNow! optimized client for SETI too? Your D-40 for Einstein is great....
Thank you again.
I visited the message boards
)
I visited the message boards yesterday for the first time in a few months and was intrigued to see that there was an optimised client for Einstein. After reading through the various threads I replaced the standard Albert4.37 app with S39L on a P4 Prescott @ 3.2Ghz. Processing times have dropped from an average of 30k secs/wu to about 6.5k secs/wu. Some of the newer ones have been validated already so all looks well. Amazing indeed!
Get BOINC WIKIed
RE: I visited the message
)
And this should be strong encouragement to read the msg boards more often; you never know what transpires and how it effects you.
RE: Well, I examined some
)
Few things are still occupying my mind.
1) Did you (also) take a closer look at LHC@H regarding optimization?
2) When will there be a SSE2 E@H app.?
I hope I'm not too demanding. ;)
RE: RE: Well, I examined
)
Oh not all dear, to make SSE2 work, he just needs to pony up $$$ to pay for a compiler.
From your post on the SETI forums about donations... I do not think you are willing to help either. >:( http://setiathome.berkeley.edu/forum_thread.php?id=29103&nowrap=true
Overclock with the MSI G31M3-L and Intel E8600 3.33Ghz
Intel D865GLC Socket 478 Motherboard Review
Overclock your ASUS 1005HA netbook and crunch more
[way off topic] RE: From
)
[way off topic]
To me there is no difference between people who own some green badge and people who don't. Everybody contributes in a way of their ability. Period.
And if you feel comfortable by minusing, well, have fun.
[/way off topic]
RE: I visited the message
)
Yes, you're Prescott will love 39L :)
me-[at]-rescam.org
RE: RE: Well, I examined
)
1, Not yet.
2, I don't know. SSE2 would be good for a 1-2% faster code. :-)
RE: RE: 1) Did you (also)
)
Unfortunately, they won't allow you to. I posted the question two weeks ago on L@H crunchers corner. Considering tremendous amount of data that LHC will produce this is the right time to consider ways to make processing effective.
The answer was that the program is written in Fortran and that it would be difficult to make any comparison between their official and an optimised version.
Actually, just now I came to the idea that they didn't understand my question. I was not interested in optimizing L@H (as they probably understood) but in new application that must come to process data from Collider. L@H has a limited lifetime but the application I have in mind would/ will be a real challenge.
RE: RE: I visited the
)
For clarity I should say that since its a HT processor thats 2 wu's every 6.5k secs , so a real average would be 3.25k secs/wu.
If I was one of the developers of Einstein I'm not sure if I would be pleased about this development or embarrassed. From other posts it seems that this client will be adopted as the official one so it must be more of the former and not the latter. Kudos to the Einstein team.
On a related note is BOINC capable of distributing different version of the science app based on the client cpu type?
Get BOINC WIKIed
RE: 00109404: 8B 4C DE 80
)
Ok, it seems I returned too late to download this update so I applied patch by hands. Patched version finished current WU successfully but all others finished with error immediately. So this version is not for Athlon XP.
Very sad news for SETI crunchers :( Your SETI_K78 outperforms both Crunch3r's SSE2&3 versions on all Athlon 64/ Pentium 4 I have to install it.
It's amazing, thank you very much!
Maybe you would consider possibility of creation 3DNow! optimized client for SETI too? Your D-40 for Einstein is great....
Thank you again.