I was just thinking about the source code at https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt/Xbranch/client/alpha
Right now zi3v is listed as PetriR_raw3. With Jason MIA, who are we going to get to post the next code?
It would be nice to change PetriR_raw3 to maybe PetriR_zi3v, and just add a new folder with the next release in it, maybe PetriR_V0.97.
Providing of course, V0.97 fixes the Arecibo shorty problem and doesn't create any new problems.
In case you missed it, there is a Mac in the Top Ten at SETI....

so memory overclock is more beneficial to the SETI work unit cruch times than gpu core overclock?

i would have thought it would be all about core speed.

./keepP2 device=N &

@Petri, can you explain simply what the new tuning parameter in the latest 0.96 Beta does. I am referring to:

{Using default pulse Fft limit (-pfl 64)} in the stderr.txt output for a task. This seems to be a new parameter not mentioned in the original x41zi or x41p_zi3v notes.

Can you run a cpu benchmark? Does it produce values typical for a TR? Does a memory benchmark produce proper values for the rated speed? What numbers do you get if you run the BOINC benchmark again? I would first confirm the cpu is good before looking at what might be wrong with the cpu app.

I don't know if it is the difference in SMT (or HT) as Intel calls it or simply the difference in architecture between Ryzen and Intel Broadwell-E. But the Ryzens kick butt on the cpu tasks compared to the i7-6850K that runs 300 Mhz faster. I always heard that Intel had superior math performance. Sure not seeing it on my example.

Windows scheduler has affinity property that allows to pin process to particular logical CPU. So it's possible to group CPU processes on one real core while GPU processes allocate to anotehr real CPU core.

#!/bin/bash

for (( ; ; ))
do
  schedtool -a 1,2,3,4 `pidof setiathome_x41zc_x86_64-pc-linux-gnu_cuda65_v8`
  schedtool -a 1,2,3,4 `pidof ap_7.01r2793_sse3_clGPU_x86_64`
  schedtool -a 1,2,3,4 `pidof axo`
  schedtool -a 6,7,8,9,10,11 `pidof MBv8_8.22r3712_avx2_x86_64-pc-linux-gnu`
  schedtool -a 5 `pidof compiz`
  sleep 2

done
	

i'm considering trading up 2 of my systems from dual 1060's (3gb) to single 1080ti's

looks like a single 1080ti will do about the same or maybe a little more work than 2x 1060's, is that right? I'm using the lunatics optimizations currently with some pretty aggressive command line options, and will probably go more aggressive on the 1080ti's

thoughts?

I have it in the app_info, but, it's not showing up on any of the machines. Looking at the confsettings.cpp, what else needs changing besides the g_pfFftLimit;
//defaults for long pulsefinds, need to be set at runtime in InitConfig()
int pfBlocksPerSM = 0;
int pfPeriodsPerLaunch = 0;
int pfPeriodsPerLaunch2 = 1;
int g_pfFftLimit = 512;
int unroll = 0;
bool chirpInAdvance = false;

Also, for some reason my standard Arecibo shorties in the benchmark app are overflowing when they shouldn't. What's strange is the shortened Arecibo versions from Lunatics aren't overflowing, just the ones I grabbed from BOINC long ago. They work fine with zi3xs3 and the other older apps in the benchmark app.

A few numbers that may be of Interest;

KWSN-Darwin-MBbench v2.1.07
Running on TomsMacPro.local at Mon Jul 16 03:56:03 2018
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Listing wu-file(s) in /testWUs :
blc01_2bit_guppi_58227_05169_HIP53229_0012.32686.818.22.45.80.vlar.wu blc16_2bit_guppi_58185_76028_Dw1_off_0033.2471.1636.22.45.95.vlar.wu

Listing executable(s) in /APPS :
setiathome_x41p_V0.93_x86_64-apple-darwin_cuda91

Listing executable in /REF_APPs :
setiathome_x41p_zi3v_x86_64-apple-darwin_cuda90
---------------------------------------------------
Current WU: blc01_2bit_guppi_58227_05169_HIP53229_0012.32686.818.22.45.80.vlar.wu
---------------------------------------------------
Skipping default app setiathome_x41p_zi3v_x86_64-apple-darwin_cuda90, displaying saved result(s)
Elapsed Time: ………………………………… 177 seconds
---------------------------------------------------
Running app with command : setiathome_x41p_V0.93_x86_64-apple-darwin_cuda91 -nobs -device 0
      129.03 real       112.83 user        14.00 sys
Elapsed Time : ……………………………… 129 seconds
Speed compared to default : 137 %
-----------------
Comparing results
Result      : Strongly similar,  Q= 100.0%
---------------------------------------------------
Done with blc01_2bit_guppi_58227_05169_HIP53229_0012.32686.818.22.45.80.vlar.wu.
Current WU: blc16_2bit_guppi_58185_76028_Dw1_off_0033.2471.1636.22.45.95.vlar.wu
---------------------------------------------------
Running default app with command : setiathome_x41p_zi3v_x86_64-apple-darwin_cuda90 -nobs -device 0
      218.56 real       192.27 user        24.04 sys
Elapsed Time: ………………………………… 218 seconds
---------------------------------------------------
Running app with command : setiathome_x41p_V0.93_x86_64-apple-darwin_cuda91 -nobs -device 0
      155.52 real       135.54 user        17.80 sys
Elapsed Time : ……………………………… 156 seconds
Speed compared to default : 139 %
-----------------
Comparing results
Result      : Strongly similar,  Q= 100.0%
---------------------------------------------------
Done with blc16_2bit_guppi_58185_76028_Dw1_off_0033.2471.1636.22.45.95.vlar.wu.

Done with Benchmark run! Removing temporary files!

For Emphasis;
Speed compared to default : 137 %
Speed compared to default : 139 %