Forum > Windows

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

<< < (4/7) > >>

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! ;D

Urs Echternacht:

--- Quote from: Simon on 14 Nov 2006, 04:38:59 pm ---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.

--- End quote ---

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:

--- Quote from: BenHer on 15 Nov 2006, 01:28:04 am ---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 ;)
--- End quote ---
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

Navigation

[0] Message Index

[#] Next page

[*] Previous page