Thanks for checking - I'll grab some coffee and head downstairs to investigate.

I have a few questions.

And here are the answers.

I wonder why they are still in the installer and why they are extracted?

They're extracted because they're still in the installer - the process is "deploy all files found in the stated folder". And they were still in the folder because I forgot to delete them while updating - finger fumble. Slight additional payload to download, no other penalty. Now deleted from build system, won't appear in next version.

Is the file dated 31.07.2016 used for any selection in the installer?

I downloaded a fresh copy of all three r3500 applications from Raistmer's mail.ru dropbox, and repeated your comparisons on a different machine.

Same conclusion - the kernels for ATi_HD5 and NV_SoG are identical, the kernels for ATi (base version) are newer and larger. I don't know why - I'll draw it to Raistmer's attention (his department, not mine) - I think it simply confirms that development work is ongoing, and none of these apps is finally certified for prime time yet. Which is why this is still a Beta.

The {newer, larger} version will certainly be deployed if the ATi base version app is selected via the UI. The installer logic processes ATi before NV, and the duplicate file handler is set at "SetOverwrite ifnewer". So the SoG version will also use the {newer, larger} version if it is installed in the same installer run with the ATi base version: if SoG is selected on its own, or in conjunction with ATi_HD5, the older version will be the only one deployed.

That feels all wrong, but again it's Raistmer's department: I'll remind him that if he updates a file, he has to increment the version number too.

Is <api_version>7.5.0 compatible with BOINC 6.10.58 

We had a long discussion about this at SETI Beta recently, because TBar tripped over a missing back-compatibility in Jason's X-branch CUDA code.

Basically, the problem is that there was a (very slow, very gradual) transition between two different ways for the BOINC client to tell the science application which of the multiple GPUs in the computer BOINC has set aside for a newly-starting science task. BOINC v6: by command line, BOINC v7 (starting with v7.1.0): via an init_data.xml file.

The two systems ran in parallel for some four years, but the command line version was finally disabled two years ago because it was incompatible with a Bitcoin Utopia application that they couldn't modify (yes, really. That's how complicated compatibility gets in this world. Welcome to what used to be known as 'DLL Hell'.)

But I'm pretty certain that Raistmer uses a "new enough" API these days, and handles the fallback to ancient clients OK. v6.10.58 was released 01-Jul-2010 11:55, so it's over six years old now, and it doesn't contain proper native OpenCL detection and scheduling: people shouldn't really be trying to use it with Raistmer's apps anyway.

Some people have reported difficulty choosing the right download file from OneDrive.

This is the view I use:



Select it this way:



Hope that helps.

On the other OneDrive view you can always right click and select details to see what the full name is

---

Life is what you make of it :-)

When i'm good i'm very good , but when i'm bad i'm shi#eloads better ;-) In't I " buttercups " p.m.s.l at authoritie !!;-)

For me your images don't show, I changed your links:
(I used the same view yesterday, but sorted by date)

Some people have reported difficulty choosing the right download file from OneDrive.

This is the view I use:



Select it this way:



Hope that helps.

---

 


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

. . Thanks Richard, that clarifies things. Just need to spread the word to non-onedrive users like myself.

...but if you see big positive change over default please report.

So i read it in the documentation (old perhaps).

actual settings are -tune 2 1 1 64 i was wrong before(1,2,1,64)

i got a speed increase by one workunit (SoG/non Guppi) of ~300 seconds faster that before,

truly i overclocked the gpus memory by 200Mhz, but thats not much effecting the results too much, or too ?

Divers 356.45 , GTX 670 , Windows 7 , freeing up 2 cores or less has no effect.

Besides they´re vulkan drivers

Greetings

It´s the kernel ID i changed , what´s that ?

---

...but if you see big positive change over default please report.

So i read it in the documentation (old perhaps).

actual settings are -tune 2 1 1 64 i was wrong before(1,2,1,64)

i got a speed increase by one workunit (SoG/non Guppi) of ~300 seconds faster that before,

truly i overclocked the gpus memory by 200Mhz, but thats not much effecting the results too much, or too ?

Divers 356.45 , GTX 670 , Windows 7 , freeing up 2 cores or less has no effect.

Besides they´re vulkan drivers

Greetings

It´s the kernel ID i changed , what´s that ?

This depends on memory timing and is always host dependent.
Tuning Kernel 2 sometimes gives speed up but not always.
Thats the reason i wrote testing required in the read me.
More important in this case is you now have work group size of 64 instead of 128.
Thats probably speed up in your case.
Would be most probably the same if you`d use 1 1 1 64.
This option was tested only and ATI GPU`s back then.

On my old HD 7970 i had tune option for both kernel 1 and kernel 2 for example.

On NV work group size of 256 or 512 should be faster.
AMD GPU`s only have wG of 256 whilst most modern NV GPU`s have 1024.

---

With each crime and every kindness we birth our future.

More important in this case is you now have kernel size of 64 instead of 128.

yeah, that why on 128 the percentage display got stuck for more than 10 seconds, i don´t wana wait on results ;D

Edit:

i´ll check that out...

---

. . Thanks Richard, that clarifies things. Just need to spread the word to non-onedrive users like myself.

I also don't use onedrive. I'm not sure if Windows Vista even supports onedrive.

. . Thanks Richard, that clarifies things. Just need to spread the word to non-onedrive users like myself.

I also don't use onedrive. I'm not sure if Windows Vista even supports onedrive.

Provided it supports a web browser, I think it should be able to reach the download address.

. . Thanks Richard, that clarifies things. Just need to spread the word to non-onedrive users like myself.

I also don't use onedrive. I'm not sure if Windows Vista even supports onedrive.

Provided it supports a web browser, I think it should be able to reach the download address.

I tried it. It was able to reach this web page, which still has about half of each file name hidden (at least under my Mozilla Firefox browser).

https://onedrive.live.com/?authkey=%21AK7t%2D36P9nAec2Y&id=8D83BF774A4A86F5%21979&cid=8D83BF774A4A86F5

I tried it. It was able to reach this web page, which still has about half of each file name hidden (at least under my Mozilla Firefox browser).

https://onedrive.live.com/?authkey=%21AK7t%2D36P9nAec2Y&id=8D83BF774A4A86F5%21979&cid=8D83BF774A4A86F5

If you do as Richard suggested in his earlier post and select the List view you'll be able to see the full file name for each file.

---

Grant
Darwin NT

. . Hi Richard,

. . Now that WOW is over for another year I have run Beta(4) on my little donkey (3.0GHz C2D E7600 with nvidia GT730). I shut down BOINC first then ran it. As usual the install was seamless. The only thing that surprised me was that while I selected SoG r3500 and there is no SoG section in my app_config.xml it appears to be still following the config for CUDA50 and is still running 2 WU on GPU.

. . But just letting you know install was AOK.

. . Stephen

. . Now that WOW is over for another year I have run Beta(4) on my little donkey (3.0GHz C2D E7600 with nvidia GT730). I shut down BOINC first then ran it. As usual the install was seamless. The only thing that surprised me was that while I selected SoG r3500 and there is no SoG section in my app_config.xml it appears to be still following the config for CUDA50 and is still running 2 WU on GPU.

It depends how you set up your app_config.xml file. I ended up using

<app_config>
   <app>
      <name>setiathome_v8</name>
      <gpu_versions>
          <gpu_usage>.50</gpu_usage>
          <cpu_usage>.04</cpu_usage>
      </gpu_versions>
   </app>

   <app_version>
       <app_name>setiathome_v8</app_name>
       <plan_class>opencl_nvidia_SoG</plan_class>
       <avg_ncpus>1.0</avg_ncpus>
       <ngpus>1.0</ngpus>
   </app_version>
</app_config>

Note that the first section sets up the device usage for all setiathome_v8 GPU versions. The second section sets up different (override) values for the opencl_nvidia_SoG <plan_class>. And I don't have an entry for cuda50 anywhere.

So, what happens when you switch applications in mid-flow? Previously cached tasks will still have the cuda50 labeling, so will use (in my case) the generic settings - even though the installer-generated app_info.xml file will direct BOINC to run the SoG application for these tasks. Newly fetched work will be labeled opencl_nvidia_SoG. and the bespoke setting in app_config will come into play when those tasks are reached. Another benefit of using a short cache when experimenting with new applications.

. . Now that WOW is over for another year I have run Beta(4) on my little donkey (3.0GHz C2D E7600 with nvidia GT730). I shut down BOINC first then ran it. As usual the install was seamless. The only thing that surprised me was that while I selected SoG r3500 and there is no SoG section in my app_config.xml it appears to be still following the config for CUDA50 and is still running 2 WU on GPU.

It depends how you set up your app_config.xml file. I ended up using

<app_config>
   <app>
      <name>setiathome_v8</name>
      <gpu_versions>
          <gpu_usage>.50</gpu_usage>
          <cpu_usage>.04</cpu_usage>
      </gpu_versions>
   </app>

   <app_version>
       <app_name>setiathome_v8</app_name>
       <plan_class>opencl_nvidia_SoG</plan_class>
       <avg_ncpus>1.0</avg_ncpus>
       <ngpus>1.0</ngpus>
   </app_version>
</app_config>

Note that the first section sets up the device usage for all setiathome_v8 GPU versions. The second section sets up different (override) values for the opencl_nvidia_SoG <plan_class>. And I don't have an entry for cuda50 anywhere.

So, what happens when you switch applications in mid-flow? Previously cached tasks will still have the cuda50 labeling, so will use (in my case) the generic settings - even though the installer-generated app_info.xml file will direct BOINC to run the SoG application for these tasks. Newly fetched work will be labeled opencl_nvidia_SoG. and the bespoke setting in app_config will come into play when those tasks are reached. Another benefit of using a short cache when experimenting with new applications.

. . Yes, running the cache down might have been a very good idea. I still had a fairly full cache from WOW :(

. . I like that there is always something new to learn. I guess for now the quick solution is to modify the CUDA50 section to run singles. I will add the SoG section for when new work does arrive.

. . Actually I just thought, what if I edit client_state.xml to replace the cuda headers with SoG headers?

.

Actually I just thought, what if I edit client_state.xml to replace the cuda headers with SoG headers?

Check that the <version_num> entries are right for that before you start, else it's a bigger switch.

For WOW, I set up a bespoke app_info.xml file with both cuda50 and SoG applications - just a single app_version for each, with the same version_num, because I wasn't needing to cater for all the various upgrade paths from stock and previous Lunatics versions.

Under those controlled conditions, all you need to do is replace the line

<plan_class>cuda50</plan_class>

with

<plan_class>opencl_nvidia_SoG</plan_class>

in the <result> section of each task, or vice-versa. That allowed my machines to process guppies with SoG, and Arecibo tasks with CUDA (getting a couple of CPUs back): I kept Notepad++ open through the fortnight, with the global 'Replace' dialog open, and a couple of times a day stopped BOINC to switch over the tasks I wanted to run with the alternate application.

Actually I just thought, what if I edit client_state.xml to replace the cuda headers with SoG headers?

Check that the <version_num> entries are right for that before you start, else it's a bigger switch.

For WOW, I set up a bespoke app_info.xml file with both cuda50 and SoG applications - just a single app_version for each, with the same version_num, because I wasn't needing to cater for all the various upgrade paths from stock and previous Lunatics versions.

Under those controlled conditions, all you need to do is replace the line

<plan_class>cuda50</plan_class>

with

<plan_class>opencl_nvidia_SoG</plan_class>

in the <result> section of each task, or vice-versa. That allowed my machines to process guppies with SoG, and Arecibo tasks with CUDA (getting a couple of CPUs back): I kept Notepad++ open through the fortnight, with the global 'Replace' dialog open, and a couple of times a day stopped BOINC to switch over the tasks I wanted to run with the alternate application.

. . That is very clever. I like lateral thinking. I will have to check that SoG r3500 still like MB 812 tasks.

Actually I just thought, what if I edit client_state.xml to replace the cuda headers with SoG headers?

Check that the <version_num> entries are right for that before you start, else it's a bigger switch.

For WOW, I set up a bespoke app_info.xml file with both cuda50 and SoG applications - just a single app_version for each, with the same version_num, because I wasn't needing to cater for all the various upgrade paths from stock and previous Lunatics versions.

Under those controlled conditions, all you need to do is replace the line

<plan_class>cuda50</plan_class>

with

<plan_class>opencl_nvidia_SoG</plan_class>

in the <result> section of each task, or vice-versa. That allowed my machines to process guppies with SoG, and Arecibo tasks with CUDA (getting a couple of CPUs back): I kept Notepad++ open through the fortnight, with the global 'Replace' dialog open, and a couple of times a day stopped BOINC to switch over the tasks I wanted to run with the alternate application.

. . I moved some guppi tasks from the CPU queue to the GPU queue as SoG and worked AOK.

.

Hi,

May I ask what does "Signal on GPU" mean? We've been testing signals on GPUs for years, haven't we? What changed?

Regards,
Georgi

---