New Apps based on Code Revision 2.0 'Ni!' have been released

[Geek@Play]

Congratulations to Simon and all who have contributed to the new release 2.0.  I have been using it since last night and it seems to be a bit faster so I am very pleased with it.  Note that I am running with a cache and so the outage last night at Seti was a non event for me but I'm still trying to return the results that I crunched.

Thanks to all of you for your hard work!

[Urs Echternacht]

The problem with modifying your app_info.xml when you have already downloaded WUs BOINC thinks are for 5.17 is that it will not find the entry and error them out.

So before you edit your file, please run your cache dry with "no new tasks" "keine neuen aufgaben zulassen".

When you have crunched all WUs, then shut down BOINC and edit/remove the entry. Then start it up and it will be fine.

HTH,
Simon.

That is one way. The hard way is a bit faster. You would have to edit app_info.xml, and client_state.xml and client_state_prev.xml But this is not recommended, because it can cause failure of BOINC if you do a mistake.

I have put the new Seti-app on some of my machines today and crunched a few wus. I see a 12%-13% increase on my Pentium M (that cuts another 1100secs from 61cr wu) compared to the previous version Rev.1.3.
Nice work and a big thank you to all you optimizers over here.

Two points of criticism:
a. rough output at stderr is bad readable (very minor issue)
b. where is the actual source code? (GPL)
 

[BenHer]

Simon will post the code soon I imagine, it is allways our intention at KWSN.

However, if you want to pester someone about Open Source go ask Seti-USA...they are Allways happy to supply their source

[Dirk Sadowski]

Simon will post the code soon I imagine, it is allways our intention at KWSN.
However, if you want to pester someone about Open Source go ask Seti-USA...they are Allways happy to supply their source

Yes, you are right!



Hello!

Can somebody please explain what does this all mean in the "<stderr_txt>"?
That the people know, what they have done...
In this thread, or maybe better, somewhere on the homepage?


Greetings!



<stderr_txt>
ChirpData--[TrigArray]:  17202812 (chosen)
 GetPeak--[hand_opt]:      2978 (chosen)
   f_sum--[original]:     27790 (chosen)
GetChiSq--[hoisted+abs(]:     36081 (chosen)
IPP FFT SSE2(64K)[original]:   5774918 (chosen)
Bench Time: 2.41 seconds
work_len=1048576
Optimized Windows SETI@Home Enhanced application

Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
  Version: Windows SSE2 32-bit based on seti V5.15  'Chicken Good!'
      Rev: (R-2.0|QxB|FFT:IPP_SSE2|Ben-Joe|)
    CPUID: 'AMD K8 Athlon 64 (Newcastle)'
     cpus: 1 cores: 1 threads: 1   cache: L1=64K  L2=512K L3=0K
 features: mmx 3Dnow 3Dnow+ sse sse2 
    speed: 2211 MHz  -- read megs/sec: L1=12107, L2=5882, RAM=2512

Work Unit Info
True angle range:  7.932342

Spikes Pulses Triplets Gaussians Flops
    2       0        1          0       3227178515016
</stderr_txt>

[BenHer]

     ChirpData--[TrigArray]:  17202812 (chosen)
        GetPeak--[hand_opt]:      2978 (chosen)
          f_sum--[original]:     27790 (chosen)  }- optimized functions - many versions of each [ <name> ] = fastest
   GetChiSq--[hoisted+abs(]:     36081 (chosen)
IPP FFT SSE2(64K)[original]:   5774918 (chosen)

Bench Time: 2.41 seconds  - Time to complete all testing

work_len=1048576   leftover debugging

Optimized Windows SETI@Home Enhanced application

      Rev: (R-2.0|QxB|FFT:IPP_SSE2|Ben-Joe|)  Revision - Compile option - FFT used - Who incorporated whos code 

read megs/sec: L1=12107, L2=5882, RAM=2512 - How fast memory test could read  from L1, L2 caches and RAM in Megabytes per second

[rgathright]

I ran the V2.0 all night, but unfortunately it slowed down my processing.  You can follow the link I posted above and easily see my WU results.

I do like V2.0 for one reason, I notice I had maybe 200,000 page faults per WU (comparing active results when I looked this morning).  When I started the old client up again, 25 minutes later I have 5,400,233 page faults for one WU.  Yet for some reason the old client is faster.   

[Simon]

Like Ben and I posted above, Reuben, the 2.0 release is not meant for Core 2 / Woodcrest / Merom systems (I did note that in the original announcement  ). For whatever reason (we're not 100% sure yet either), the 1.3 and 1.41 apps perform more quickly on those systems.

Go to the downloads section and grab the Intel Core 2 SSSE3 optimized version from the 1.3 section for now instead, please.

HTH,
Simon.

[Dirk Sadowski]

BenHer thanx for explanation!



BTW.
AMD K7 Athlon 600:

True angle range: 0.421940

Windows optimized S@H Enhanced application by Crunch3r
Version info: Windows MMX V5.12 by Crunch3r
CPU time 97124

Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows MMX 32-bit based on seti V5.15 'Chicken Good!'
Rev: (R-2.0|QxB|FFT:IPP_SSE2|Ben-Joe|)
CPU time 77395

5 h 29 min. faster!


Thanx to all optimizers!
Very good work!


Greetings! 



EDIT:

AMD K8 3200+

True angle range: 0.426463

SUSE Linux 10.1 -64Bit
Linux optimized S@H Enhanced application by Crunch3r
Version info: Linux x86_64 SSE2 64 bit V5.12 by Crunch3r
CPU time 12555

WinXP -32Bit
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows SSE2 32-bit based on seti V5.15 'Chicken Good!'
Rev: (R-2.0|QxB|FFT:IPP_SSE2|Ben-Joe|)
CPU time 11330

20 min. (+25 sec. ) faster!

Unbelievably !!!!! 

[Simon]

Yeah, it's pretty quick...

Thank Ben Herndon, Joe Segur and Alex Kan

Regards,
Simon.

[MikeK]

Thank you guys.

The new app runs around 20% faster on my X2 4800 standard core speed.
With 1.3 ~ 12000 sec. with 2.0 ~ 9000 seconds.
Now will see with overclocked speed.

regards Mike

[Kna]

Another big thanks to all the guys which have allowed to this new optimised revision to exist   

But a strange behaviour with my Intel SSE only CPUs ?
Rev 2.0 seems to be on average 10% slower than rev 1.3 or Crunch3r SSE app, at similar AR.

K7 CPUs seems not to be affected. Due to different architecture, or DDR instead of PC133 SDRAM ? Mystery..

Does anybody notice the same thing ?

[Simon]

Not really, Franck -

though I have to say that I didn't test on SSE-only systems a lot (though other people did and reported good success). Thing is, they all used AMD CPUs, so I really lack results using P3s.

If the new apps don't work as quickly as the old ones, the logical step would be to downgrade

Regards,
Simon.

[Kna]

Yes Simon, downgrade allready done, even if I don't have entensive measurements of this slowdown.
It was simply not nice to see   

Old PIII and Celeron desktops would be upgraded to P4 soon, the last survivors will be some dual PIII servers which suffice for their tasks for a few times.

I've downgraded to Crunch3r SSE, allready the fastest app for Intel PIII familly if I'm not mistaken, but Monday I put previous Chicken everywhere.
After some recent Crunch3r's post in Berkeley forum, his apps are banned from my rigs. But it's another story 

Regards,
Franck.

[Furex]

Great stuff!

Hope to see R2.0 for linux soon 

[ntorcida]

I am having Amd Athlon 64 3000+ (venice core). Should I use SSE or SSE2 Generic? Curently I am using SSE2 Generic....