Famous Akosf Results with S39L per WU
original__________S39______________S39L
8-10 hours________2h07min__________1h27min
*******************************************
PC Pentium4, 2,6GHz, 1GB RAM, Windows XPHome, ServicePack2
I'm now seeing completed quora for my S39L WUs. Claimed credits are peanuts. Actuals are typically 3.5 to 4 times the claims! I'm starting to feel guilty...
Average up to now 19,000 sec.
First result with S39L - 5400 sec.
Still pending, let's see what the validation shows.
If it's allright, I can say only that it's the work of a master.
Average up to now 19,000 sec.
First result with S39L - 5400 sec.
Still pending, let's see what the validation shows.
If it's allright, I can say only that it's the work of a master.
Code of CPDN is worthless. (just my opinion)
I think a better compiler would be able to increase its speead about 30-50%. (careful estimate)
The handoptimizing is a bit hopeless because of very big code and the very slow feedback. (validation)
SETI has some very good optimised code.
I spent an afternoon to optimise it, and I could get just 10% improvement. (Crunch3r's Athlon XP SSE 2.09)
SZTAKI code is very slow.
I tried to optimise it (11th dimension) and my code was about 5 times faster, but I found a security problem, like as seti@home classic. My proposal was deleted on the message board.
PrimeGrid. I spent just some seconds to optimize it and I get ~250% improvement. But there are much more faster algorithms (my binary based searcher was about 1000 times faster, so it means that my duron would be able to find the solution in about 1 billion years.)
So, this project is a planetheater... (just my opinion)
So 30 or 40 days from now when the S4 search is done, what project(s) would you recommend we devote our CPU time to? Who does the most science / useful calculation per clock cycle? Are any of the medical projects more code-efficient than the others you have mentioned?
(P.S. Thanks for your work here - my Athlon XP 2800+ is around 4200 secs /WU under S39L)
Code of CPDN is worthless. (just my opinion)
I think a better compiler would be able to increase its speead about 30-50%. (careful estimate)
The handoptimizing is a bit hopeless because of very big code and the very slow feedback. (validation)
SETI has some very good optimised code.
I spent an afternoon to optimise it, and I could get just 10% improvement. (Crunch3r's Athlon XP SSE 2.09)
SZTAKI code is very slow.
I tried to optimise it (11th dimension) and my code was about 5 times faster, but I found a security problem, like as seti@home classic. My proposal was deleted on the message board.
PrimeGrid. I spent just some seconds to optimize it and I get ~250% improvement. But there are much more faster algorithms (my binary based searcher was about 1000 times faster, so it means that my duron would be able to find the solution in about 1 billion years.)
So, this project is a planetheater... (just my opinion)
So 30 or 40 days from now when the S4 search is done, what project(s) would you recommend we devote our CPU time to? Who does the most science / useful calculation per clock cycle? Are any of the medical projects more code-efficient than the others you have mentioned?
(P.S. Thanks for your work here - my Athlon XP 2800+ is around 4200 secs /WU under S39L)
As I read it, then the S5 esearch are ready to go when the current S4 search is finished, but I could have misread it all.
PrimeGrid. I spent just some seconds to optimize it and I get ~250% improvement. But there are much more faster algorithms (my binary based searcher was about 1000 times faster, so it means that my duron would be able to find the solution in about 1 billion years.)
So, this project is a planetheater... (just my opinion)
Incredible! Did you get any feedback about this huge improvement?
I'm now seeing completed quora for my S39L WUs. Claimed credits are peanuts. Actuals are typically 3.5 to 4 times the claims! I'm starting to feel guilty...
I run trux's calibrating client for this reason. Otherwise folks running the distributed ap will start to get caught in quora with folks running the optimized ap and be discouraged by the sudden drop in their credit. If you are interested, see truXoft Calibrating Client
RE: Famous Akosf Results
)
My Athlon XP-M (Barton
)
My Athlon XP-M (Barton core)
64K L1, 512K L2 Cache
O/C 25% to 2.5Ghz
S39> 3414 sec; S39L > 3343 sec
97.92%
overall, from official > S39L 25.68%, almost 4X improvemant.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
I'm now seeing completed
)
I'm now seeing completed quora for my S39L WUs. Claimed credits are peanuts. Actuals are typically 3.5 to 4 times the claims! I'm starting to feel guilty...
Athlon XP 2000+ 512
)
Athlon XP 2000+
512 MB
Average up to now 19,000 sec.
First result with S39L - 5400 sec.
Still pending, let's see what the validation shows.
If it's allright, I can say only that it's the work of a master.
RE: Athlon XP 2000+ 512
)
The result is allright.
Anders n
RE: Code of CPDN is
)
So 30 or 40 days from now when the S4 search is done, what project(s) would you recommend we devote our CPU time to? Who does the most science / useful calculation per clock cycle? Are any of the medical projects more code-efficient than the others you have mentioned?
(P.S. Thanks for your work here - my Athlon XP 2800+ is around 4200 secs /WU under S39L)
RE: RE: Code of CPDN is
)
As I read it, then the S5 esearch are ready to go when the current S4 search is finished, but I could have misread it all.
My AMD XP 2600+ has gone from
)
My AMD XP 2600+ has gone from ~4600 secs (S38) to ~4000 secs (S39L). I skipped S39 'cause the upgrades are coming too fast. :-P
Upgrading my XP 1600+ next.
Seti Classic Final Total: 11446 WU.
RE: PrimeGrid. I spent just
)
Incredible! Did you get any feedback about this huge improvement?
RE: I'm now seeing
)
I run trux's calibrating client for this reason. Otherwise folks running the distributed ap will start to get caught in quora with folks running the optimized ap and be discouraged by the sudden drop in their credit. If you are interested, see truXoft Calibrating Client