Forum > Discussion Forum

Report on new optimized Astropulse apps for Windows

(1/19) > >>

Leaps-from-Shadows:
On Cruiser-

v4.37 SSE3 EPF:  Slower than v4.35 SSE3 app, with a projected completion time of 31 hours or so (21.1% complete).  Slowest time for v4.35 SSE3 app was around 29 hours.

v5.00r69 SSE3:  Faster than all previous apps, with a projected completion time of 26 hours or so (63.2% complete).

I'll post more updates once the units complete.  The unit crunching with v4.37 is the last one for that app - all others have been branded for the v5.00 app.  I've got 10 of those including the one crunching (six for Main, four for Beta).  I'm currently using the v5.00r69 SSE3 app for both Main and Beta.

Richard Haselgrove:
My testing note on that build, running on a Q6600, reads "Did shave an hour+ off the runtime, though - 18:32:47 down to 17:16:42.": which is why I chose it for the release (final build in the ongoing quest for v4 optimisation, before programming effort switched to v5.00 compatibility).

Since v4 is now effectively dead, I think the only sensible thing to do is to soldier on until the last one is crunched, accepting the 2 hr penalty with as much grace as you can muster (through gritted ;D, no doubt).

But it's still a useful reminder of the unpredicable variability of the optimisations on AMD versus Intel, and and indication of the sort of tests we need to run (project timing permitting) in the run up to future releases.

Raistmer:
@Leaps-from-Shadows 
could you post link on your host ?
I need timings from stderr to see what part of program become slower...

Richard Haselgrove:
I think it must be RID 1065144181 on host 4521634 (Phenom) - as yet unfinished.

Cosmic_Archer has a similar report for RID 1060056077 on host 2889590 (Opteron) - also as yet unfinished.

Raistmer:
Thanks Richard.
Unfinished tasks have no timings, so will await when they become finished :)

Navigation

[0] Message Index

[#] Next page