I found with my GTX 750Ti & GTX 1070 running the current SoG version in the Lunatics Beta v4 installer that running 1 at a time using the sample "Super clocked x50TI / x60TI" command line gave a huge boost to my output.
Running 2 or 3 at a time gave a very slight boost in output, so slight I decided it wasn't worth it, especially after getting a "Finish file present too long" error for the first time while running 3 at a time.
Running with the "High end cards x8x x80TI Titan / Titan Z" command line would hopefully give even better output from my GTX 1070, but with the GTX 750Ti in the system with it, that's not possible at this stage.

On two machines now I've dabbled with the recommended high-end command lines; with the Arecibo tasks this weekend I found the only parameter that made any real difference was sbs and it makes sense when you read Raistmer's explanation. I was going to try again when there was a glut of VLARs.

Thanks for the tips guys, I did put a command line into the latest rig with the 6 video cards, it is running SoG, so I will let it run for a while and see how it goes. I didn't realize my dual 1060 machine was running CUDA, I will uninstall and reinstall the Lunatics app, choosing SoG this time and then putting in the recommended command line from above. Hopefully it will see a significant increase in RAC, as right now (I know, it's still early) it is not yet even surpassing my machine at the in laws with a i7-4770 and a GTX 670. I know this one is just a i7 X980, but it has 12 HT cores instead of 8, is running about the same Ghz, and has double the video cards! :-O I know, give it time... ;-) Well, I will make the switch to SoG this weekend, and see what becomes of it.

---

Since you are running Windoze just re-run the installer, select the SoG option instead of the CUDA option, sit back and watch the credits light up.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Ok, I'll do that right now!

---

I would be happy to run command lines, but I would need a bit of hand holding to do so: What to put in, where to put it, etc. More than happy to try it, just not sure the specifics.

As mentioned, sample files can be found in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\docs folder in the ReadMe_MultiBeam_OpenCL_NV_SoG.txt file.

Using this one with my GTX 750Ti/GTX 1070
Super clocked x50TI / x60TI
-sbs 256 -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32
(*requires testing)


Would like to use this one, but I doubt the GTX 750TI would appreaciate it.
High end cards x8x x80TI Titan / Titan Z
-sbs 384 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64
(*requires testing)

I just copied the command line into the
mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt
file in the setiathome.berkeley.edu folder & the next time the application starts, it uses those values.

Although I like the idea of settings that don't change when you re-run the Lunatics installer that Keith is using.

Ok, I just reinstalled it. I have a question though. This system with the 2 1060s is running Win 7 64bit, and you mentioned that you are copying it into the mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file. Would I want to copy it into the mb_cmdline_win_x64_SSE3_OpenCL_NV_SoG.txt file instead. I had planned on using your

-sbs 256 -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32

for the command line, anything I might want to tweak for the 2 1060's?

---

you mentioned that you are copying it into the mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file. Would I want to copy it into the mb_cmdline_win_x64_SSE3_OpenCL_NV_SoG.txt file instead.

If that's the name of the file there, then i'd use that one.

You can check by opening up the app_info.xml file and if you look for the v8 SoG section, near the bottom of the app_version details you'll find something like this.

        <file_ref>
            <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>

where it's telling the programme what the name of the command line config file is.
The other option (which sounds like a good idea to me) was mentioned either here or in another thread (sorry I can't remember the posters name) that made use of the app_config.xml file to give the command line settings- having the big advantage that re-running the Lunatics installer won't remove any modifications or references there you've made yourself.
And if you go back to stock for whatever reason, the settings will still be applied when SoG is being used.

I had planned on using your

-sbs 256 -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32

for the command line, anything I might want to tweak for the 2 1060's?

I'd use that one as is for now, and see what Mike has to say about those settings in relation to the GTX 1060.
They certainly gave my GTX 1070 a huge boost.


EDIT- fixed up numerous typos.
Sorry, not feeling the best at present & the brain appears to be barely working.
:-/

---

Grant
Darwin NT

sorry I can't remember the posters name

Yeah that was me but Richard was the first to propose it.

I posted it somewhere in another thread but don't remember exactly at this moment.

---

The other option (which sounds like a good idea to me) ... that made use of the app_config.xml file to give the command line settings- having the big advantage that re-running the Lunatics installer won't remove any modifications or references there you've made yourself.

Lunatics installer don't touch any existing .txt file.
It do not delete them nor overwrite them.
Only if the .txt file do not exist - it puts/extracts the zero-length empty .txt file.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

The other option (which sounds like a good idea to me) ... that made use of the app_config.xml file to give the command line settings- having the big advantage that re-running the Lunatics installer won't remove any modifications or references there you've made yourself.

Lunatics installer don't touch any existing .txt file.
It do not delete them nor overwrite them.
Only if the .txt file do not exist - it puts/extracts the zero-length empty .txt file.

True, the configuration file will still be there, but the installer does replace the app_info file, and if the reference to the .txt file is changed then you loose it's settings.
I've got a 64bit OS, yet the file name I use is different to the one Al is using.

---

Grant
Darwin NT

Ok, don't remember where the original post was but you can try this

<app_config>
 <app_version>
    <app_name>setiathome_v8</app_name>
    <plan_class>opencl_nvidia_SoG</plan_class>
    <avg_ncpus>1</avg_ncpus>
    <ngpus>0.5</ngpus>
    <cmdline>insert commandline here</cmdline>
 </app_version>
 <app_version>
    <app_name>astropulse_v7</app_name>
    <plan_class>opencl_nvidia_100</plan_class>
    <avg_ncpus>0.35</avg_ncpus>
    <ngpus>0.5</ngpus>
    <cmdline>-use_sleep -unroll 28 -oclFFT_plan 256 16 256 -ffa_block 12288 -ffa_block_fetch 6144 -tune 1 64 4 1 -tune 2 64 4 1 -hp</cmdline> 
 </app_version>
</app_config>

Have fun...

Zalster

---

I've got a 64bit OS, yet the file name I use is different to the one Al is using.

I don't think he "is using" - he only asked if he should use "_x64" (as in "should I create ...?" - and the answer is No)

The file in Lunatics_Win64_v0.45_Beta4-for-SoG_setup.exe (as you can see by 7-Zip) is:
mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt

Named by _x64 are only the CPU files like:
mb_cmdline_win_x64_AVX_VS2010.txt

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

<cmdline>insert commandline here</cmdline>

Do you think he will really see this?

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I've learn never to leave anything to chance, lol...

---

So,it should look something like this:

<app_config>
 <app_version>
    <app_name>setiathome_v8</app_name>
    <plan_class>opencl_nvidia_SoG</plan_class>
    <avg_ncpus>1</avg_ncpus>
    <ngpus>0.5</ngpus>
    <cmdline>-sbs 256 -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32</cmdline>
 </app_version>
 <app_version>
    <app_name>astropulse_v7</app_name>
    <plan_class>opencl_nvidia_100</plan_class>
    <avg_ncpus>0.35</avg_ncpus>
    <ngpus>0.5</ngpus>
    <cmdline>-use_sleep -unroll 28 -oclFFT_plan 256 16 256 -ffa_block 12288 -ffa_block_fetch 6144 -tune 1 64 4 1 -tune 2 64 4 1 -hp</cmdline> 
 </app_version>
</app_config>

And the app_config goes in the BOINC or SETIathome folder? I don't do these enough to remember. Do I also still put that command line into the cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file as well as doing the app_config.xml file? Or just one or the other? Thanks!

---

And the app_config goes in the BOINC or SETIathome folder?

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu

Do I also still put that command line into the cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file as well as doing the app_config.xml file? Or just one or the other? Thanks!

One or the other.

EDIT- with it in app_config.xml you'll need to restart BOINC, or just Options, "Read config files" from the manager for the settings to take effect.
With it in the cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file they'll take effect whenever the SoG application starts up (ie once one WU finishes, and the next one begins).

---

Grant
Darwin NT

Is one way better than the other? There's a lot more verbiage in the app_config file, besides that command line, so is it 'better'? Oh, and Grant, I hope you are feeling better soon. Thanks for your assistance.

---

Is one way better than the other? There's a lot more verbiage in the app_config file, besides that command line, so is it 'better'?

If (for some reason) the name of the configuration file changes then you'd need to change the name of your file, or the reference to it in app_info.xml. Or if you go back to stock, then those settings won't have any effect when SoG runs.
With it in app_config the main advantage is that no matter what happens to the app_info.xml file, your settings are still there & will take effect whenever the referenced application runs.
With it in the MB_config file, to change it all you have to do is clear out what's there & post the new command line, with it in the app_config file you need to make sure you don't mess up anything else while you're in there.
The arguments for doing either way are both pretty strong, really it just comes down to personal choice.

Oh, and Grant, I hope you are feeling better soon. Thanks for your assistance.

Thanks.
Blood results this Thursday, with luck they'll find something & we can get it sorted. Otherwise it's more tests or things just come good with us having no idea WTF was going on.

---

Grant
Darwin NT

Bummer about that one. But wait, aren't you down in Oz? The land of 10,000 things that will kill you? Maybe some little creepy crawly snuck up on you in your sleep? :-O Gawd, I hope not, you're much too valuable resource here to be taken out by something like that! ;-) Seriously, hope they get it nailed down for you soon, and you're back to 100% soon.

Oh, and while waiting for your definitive answer, I started with adding the command line to that .txt file, and restarted BOINC. It looks to be running them somewhere around 8 minutes or so, and this is while using 0.04 CPUs, and running one task per card. Is this about the expected time for this setup? Should I bump it up to more than 1 task/card at a time, add a bit more CPU, or just wait for a bit to see what the results of adding the command line are?

---

Is the

<cmdline>-use_sleep -unroll 28 -oclFFT_plan 256 16 256 -ffa_block 12288 -ffa_block_fetch 6144 -tune 1 64 4 1 -tune 2 64 4 1 -hp</cmdline>

a bit too aggressive for a 1060 for AP tasks? Not familiar enough with how the Pascal family handles AP yet. I would say it would be too high an unroll value for Maxwell cards other than 980, 980Ti or Titan. Not sure about the 1060. Comments?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

It looks to be running them somewhere around 8 minutes or so, and this is while using 0.04 CPUs, and running one task per card. Is this about the expected time for this setup? Should I bump it up to more than 1 task/card at a time, add a bit more CPU, or just wait for a bit to see what the results of adding the command line are?

On my system 1 WU at a time generally was best with a CPU core reserved- running more WUs did give slightly better output, but it was only slightly better & I ended up with a "Finish file present too long" error which had never occurred before, or since, after going back to 1WU at a time.

Also with the PCIe*1 connectors that might actually impact on crunching times. With CUDA50 the Bus Interface Load in GPUz was generally 0, with the odd 1-2% showing. With SoG & the command line & a CPU reserved, on my GTX 750Ti the Bus Interface Load is around 17% with spikes over 20%- which is roughly 1.5 times the maximum rate for PCIe*1


Best bet (IMHO) would be to reserve 1 CPU core per GPU WU, and just run one at a time. See how it goes for a day or 2. If it's good, then try 2 at a time & see how the run times go; the PCIe*1 speed may result in better or worse performance (have to try to actually see).
And when running more than one at a time, keep an eye out for "Finish file present too long" errors.

---

Grant
Darwin NT