Posts by MagicEye

1) Message boards : Number crunching : The last day of S@H (Message 2047831)
Posted 1 May 2020 by Profile MagicEye
Post:
I have uploaded now my last work units.
For me it was a question of honor to not abort them.

There are a lot of space related projects that i will support now more in the future (Einstein, Universe, Asteroids, Milkyway) and of course at the moment everything that is related to the COVID-19 (Folding, Rosetta, OpenPandemic(WCG, coming next).
2) Message boards : Number crunching : Flakey AMD/ATI GPUs, including RX 5700 XT, Cross Validating, polluting the Database (Message 2025577)
Posted 30 Dec 2019 by Profile MagicEye
Post:
Since yesterday, we've fallen back to the old server so anonymous platform apps should be able to get work. Since this morning we should have had the validator that requires 3 results for overflow results. Merry Christmas!

What is the difference between the old and the new validator setting?
In the past i have seen always quorum 3 if 2 hosts have different results - and this practice is still the same when i look on the today results of some 5700XT .
I just want to understand the effort - for me it stills looks the same.

From the science point of view the quorum 4 would be a very good idea to reduce the bad results marked as good by 2 5700 GPUs until a solution is found to exclude such hosts completely.
Or will the results of the 5700 GPUs be deleted in a later stage of the computing on the servers and we don't see any of these results in the science database?
3) Message boards : Number crunching : need a working app_info.xml for AMD CPU+AMD GPU with Linux (Message 2023248)
Posted 15 Dec 2019 by Profile MagicEye
Post:
OK, i copied the AP section to my app_info and it seems to work.
Die executable is not deleted and i got no error message. :)
Now i have to wait for some AP WU. And than i can do some fine tuning with the parameters.

The double __ i have noticed, but i copied the name directly from the filename.

The machine with Geforce1070ti is using the V.99 app since some days. I only updated the executable and the name in the app_info.
The app_info i have posted with nvidia was old.
And the other one with Geforce1030 stays on the old version, no need to change.

Thank you!
4) Message boards : Number crunching : need a working app_info.xml for AMD CPU+AMD GPU with Linux (Message 2023239)
Posted 15 Dec 2019 by Profile MagicEye
Post:
Thanks, but this still doesnt work for AP.

What is it the all-in-one?
I just want to use an non-standard app that i have already downloaded like for nvidia GPU and for MB app on ATI GPU.
There I only had to copy the app-files and the app_info in the Boinc folder and it worked.

The AP app is always deleted by BoincManager during start and then it complains about the missing files.
astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100 (downloaded from your link)
I have to download/copy the app again and again. Is there any way to prevent Boinc Manager from deleting the file or telling me what is wrong ?
When i dont use the app_info the app-exec is not deleted and is crunching without any problem.

The MB is working but not the AP - and i dont see any difference in the app_info - (except the file name of cource).
And i dont want to miss the AP WUs, they give much more credits...

Log:
So 15 Dez 2019 19:28:41 CET | SETI@home | [error] State file error: missing application file


This is my last version, but still defective:
<app_info>
  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG</name>
      <executable/>
    </file_info>
  <file_info>
      <name>mb_cmdline-8.22-opencl_ati5_SoG.txt</name>
  </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>opencl_ati5_SoG</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.1</avg_ncpus>
      <max_ncpus>0.1</max_ncpus>
      <file_ref>
        <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG</file_name>
        <main_program/>
      </file_ref>
      <file_ref>
       <file_name>mb_cmdline-8.22-opencl_ati5_SoG.txt</file_name>
       <open_name>mb_cmdline.txt</open_name>
      </file_ref>
    </app_version>
  <app>
     <name>astropulse_v7</name>
  </app>
     <file_info>
       <name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</name>
        <executable/>
     </file_info>
    <app_version>
      <app_name>astropulse_v7</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>708</version_num>
      <plan_class>opencl_ati_100</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.1</avg_ncpus>
      <max_ncpus>0.1</max_ncpus>
      <file_ref>
         <file_name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</file_name>
          <main_program/>
      </file_ref>
      <file_ref>
         <open_name>ap_cmdline.txt</open_name>
      </file_ref>
    </app_version>
   <app>
      <name>setiathome_v8</name>
   </app>
      <file_info>
         <name>MBv8_8.22r3711_sse41_amd_x86_64-pc-linux-gnu</name>
         <executable/>
      </file_info>
     <app_version>
     <app_name>setiathome_v8</app_name>
     <platform>x86_64-pc-linux-gnu</platform>
     <version_num>800</version_num>   
      <file_ref>
        <file_name>MBv8_8.22r3711_sse41_amd_x86_64-pc-linux-gnu</file_name>
        <main_program/>
      </file_ref>
    </app_version>
   <app>
      <name>astropulse_v7</name>
   </app>
     <file_info>
       <name>ap_7.05r2728_sse3_linux64</name>
        <executable/>
     </file_info>
    <app_version>
       <app_name>astropulse_v7</app_name>
       <version_num>704</version_num>
       <platform>x86_64-pc-linux-gnu</platform>
       <plan_class></plan_class>
       <file_ref>
         <file_name>ap_7.05r2728_sse3_linux64</file_name>
          <main_program/>
       </file_ref>
    </app_version>
</app_info>
5) Message boards : Number crunching : need a working app_info.xml for AMD CPU+AMD GPU with Linux (Message 2023206)
Posted 15 Dec 2019 by Profile MagicEye
Post:
Its a bit more than just changing the app names.
Plan-class: AMD or Ati? Ati5?
CL-files, TXT-files...

OK, here is my defective app_info:
<app_info>
  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah</name>
      <executable/>
    </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>ati5</plan_class>
      <cmdline>-nobs</cmdline>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.1</avg_ncpus>
      <max_ncpus>0.1</max_ncpus>
      <file_ref>
         <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah</file_name>
          <main_program/>
      </file_ref>
    </app_version>

  <app>
     <name>astropulse_v7</name>
  </app>
     <file_info>
       <name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</name>
        <executable/>
     </file_info>
     <file_info>
       <name>AstroPulse_Kernels_r2751.cl</name>
     </file_info>
    <app_version>
      <app_name>astropulse_v7</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>708</version_num>
      <plan_class>opencl_ati_100</plan_class>
      <coproc>
        <type>ati</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.1</avg_ncpus>
      <max_ncpus>0.1</max_ncpus>
      <file_ref>
         <file_name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</file_name>
          <main_program/>
      </file_ref>
      <file_ref>
         <file_name>AstroPulse_Kernels_r2751.cl</file_name>
      </file_ref>
      <file_ref>
         <file_name>ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_ati_100.txt</file_name>
         <open_name>ap_cmdline.txt</open_name>
      </file_ref>
    </app_version>

   <app>
      <name>setiathome_v8</name>
   </app>
      <file_info>
         <name>MBv8_8.22r3711_sse41_amd_x86_64-pc-linux-gnu</name>
         <executable/>
      </file_info>
     <app_version>
     <app_name>setiathome_v8</app_name>
     <platform>x86_64-pc-linux-gnu</platform>
     <version_num>800</version_num>   
      <file_ref>
        <file_name>MBv8_8.22r3711_sse41_amd_x86_64-pc-linux-gnu</file_name>
        <main_program/>
      </file_ref>
    </app_version>
   <app>
      <name>astropulse_v7</name>
   </app>
     <file_info>
       <name>ap_7.05r2728_sse3_linux64</name>
        <executable/>
     </file_info>
    <app_version>
       <app_name>astropulse_v7</app_name>
       <version_num>704</version_num>
       <platform>x86_64-pc-linux-gnu</platform>
       <plan_class></plan_class>
       <file_ref>
         <file_name>ap_7.05r2728_sse3_linux64</file_name>
          <main_program/>
       </file_ref>
    </app_version>
</app_info>

The only GPU app that SETI did not delete is:
setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah
There were 3 more but i dont remember the names.

The error messages:
So 15 Dez 2019 11:15:12 CET | SETI@home | Found app_info.xml; using anonymous platform
So 15 Dez 2019 11:15:12 CET | | App version needs CAL but GPU doesn't support it
So 15 Dez 2019 11:15:12 CET | SETI@home | file in app_info doesnt exist: astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100
So 15 Dez 2019 11:15:12 CET | SETI@home | file in app_info doesnt exist: AstroPulse_Kernels_r2751.cl
So 15 Dez 2019 11:15:12 CET | | app version refers to missing GPU type ati
So 15 Dez 2019 11:15:12 CET | SETI@home | [error] State file error: missing application file astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100
...
So 15 Dez 2019 11:16:32 CET | SETI@home | Sending scheduler request: To fetch work.
So 15 Dez 2019 11:16:32 CET | SETI@home | Requesting new tasks for AMD/ATI GPU
So 15 Dez 2019 11:16:34 CET | SETI@home | Scheduler request completed: got 1 new tasks
So 15 Dez 2019 11:16:34 CET | SETI@home | [error] Missing coprocessor for task blc56_2bit_guppi_58692_86262_HIP84784_0111.29417.818.21.44.26.vlar_0; aborting

The GPU is detected correct and is working without the app_info.xml
So 15 Dez 2019 11:15:12 CET | | OpenCL: AMD/ATI GPU 0: AMD Radeon VII (driver version 2841.4 (PAL,HSAIL), device version OpenCL 2.0 AMD-APP (2841.4), 16192MB, 16192MB available, 13839 GFLOPS
peak)


Another app_info that also didnt work, but contains app names:
<app_info>
  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah</name>
      <executable/>
    </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>opencl_ati5_sah</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.5</avg_ncpus>
      <max_ncpus>0.5</max_ncpus>
      <file_ref>
         <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah</file_name>
      </file_ref>
      <file_ref>
         <file_name>mb_cmdline-8.22-opencl_ati5_sah.txt</file_name>
	 <open_name>mb_cmdline.txt</open_name>
          <main_program/>
      </file_ref>
    </app_version>

  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati_sah</name>
      <executable/>
    </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>opencl_ati_sah</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.5</avg_ncpus>
      <max_ncpus>0.5</max_ncpus>
      <file_ref>
         <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati_sah</file_name>
      </file_ref>
      <file_ref>
         <file_name>mb_cmdline-8.22-opencl_ati_sah.txt</file_name>
	 <open_name>mb_cmdline.txt</open_name>
          <main_program/>
      </file_ref>
    </app_version>

  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG</name>
      <executable/>
    </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>opencl_ati5_SoG</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.5</avg_ncpus>
      <max_ncpus>0.5</max_ncpus>
      <file_ref>
         <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG</file_name>
      </file_ref>
      <file_ref>
         <file_name>mb_cmdline-8.22-opencl_ati5_SoG.txt</file_name>
	 <open_name>mb_cmdline.txt</open_name>
          <main_program/>
      </file_ref>
    </app_version>


  <app>
     <name>setiathome_v8</name>
  </app>
    <file_info>
      <name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_atiapu_sah</name>
      <executable/>
    </file_info>
    <app_version>
      <app_name>setiathome_v8</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>822</version_num>
      <plan_class>opencl_atiapu_sah</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.5</avg_ncpus>
      <max_ncpus>0.5</max_ncpus>
      <file_ref>
         <file_name>setiathome_8.22_x86_64-pc-linux-gnu__opencl_atiapu_sah</file_name>
      </file_ref>
      <file_ref>
         <file_name>mb_cmdline-8.22-opencl_atiapu_sah.txt</file_name>
	 <open_name>mb_cmdline.txt</open_name>
          <main_program/>
      </file_ref>
    </app_version>


  <app>
     <name>astropulse_v7</name>
  </app>
     <file_info>
       <name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</name>
        <executable/>
     </file_info>
     <file_info>
       <name>ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_ati_100.txt</name>
     </file_info>
    <app_version>
      <app_name>astropulse_v7</app_name>
      <platform>x86_64-pc-linux-gnu</platform>
      <version_num>708</version_num>
      <plan_class>opencl_ati_100</plan_class>
      <coproc>
        <type>ATI</type>
        <count>1</count>
      </coproc>
      <avg_ncpus>0.5</avg_ncpus>
      <max_ncpus>0.5</max_ncpus>
      <file_ref>
         <file_name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100</file_name>
          <main_program/>
      </file_ref>
      <file_ref>
         <file_name>ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_ati_100.txt</file_name>
         <open_name>ap_cmdline.txt</open_name>
      </file_ref>
    </app_version>

   <app>
      <name>setiathome_v8</name>
   </app>
      <file_info>
         <name>MBv8_8.0r3305_ssse3_x86_64-pc-linux-gnu</name>
         <executable/>
      </file_info>
     <app_version>
     <app_name>setiathome_v8</app_name>
     <platform>x86_64-pc-linux-gnu</platform>
     <version_num>800</version_num>   
      <file_ref>
        <file_name>MBv8_8.0r3305_ssse3_x86_64-pc-linux-gnu</file_name>
        <main_program/>
      </file_ref>
    </app_version>

   <app>
      <name>astropulse_v7</name>
   </app>
     <file_info>
       <name>ap_7.05r2728_sse3_linux64</name>
        <executable/>
     </file_info>
    <app_version>
       <app_name>astropulse_v7</app_name>
       <version_num>704</version_num>
       <platform>x86_64-pc-linux-gnu</platform>
       <plan_class></plan_class>
       <file_ref>
         <file_name>ap_7.05r2728_sse3_linux64</file_name>
          <main_program/>
       </file_ref>
    </app_version>
</app_info>


For the moment i get no error messages except that the apps are missing:
So 15 Dez 2019 11:26:33 CET | SETI@home | Found app_info.xml; using anonymous platform
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file mb_cmdline-8.22-opencl_ati5_sah.txt
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati_sah
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati_sah
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_SoG
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: setiathome_8.22_x86_64-pc-linux-gnu__opencl_atiapu_sah
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file setiathome_8.22_x86_64-pc-linux-gnu__opencl_atiapu_sah
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_ati_100.txt
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file astropulse_7.08_x86_64-pc-linux-gnu__opencl_ati_100
So 15 Dez 2019 11:26:33 CET | SETI@home | file in app_info doesnt exist:: MBv8_8.0r3305_ssse3_x86_64-pc-linux-gnu
So 15 Dez 2019 11:26:33 CET | SETI@home | [error] State file error: missing application file MBv8_8.0r3305_ssse3_x86_64-pc-linux-gnu

I will now run the PC a some time without app_info to get back the apps from the server.
6) Message boards : Number crunching : need a working app_info.xml for AMD CPU+AMD GPU with Linux (Message 2023136)
Posted 14 Dec 2019 by Profile MagicEye
Post:
Hello,

on my PC with GeForce i run optimized CPU apps and of course also optimzed CUDA-apps.
But on my PC with the RadeonVII i dont get any app_info.xml to work properly. So the work has to be done with stock app.
Could please someone who is using AMD CPU+ AMD GPU with optimzed app with Linux post me a working app_info.xml?

For the CPU i could take over the part from the other PC - but for the AMD GPU I have nothing.
And every try deletes me more and more of the apps and txt files...

Thanks!
Magiceye
7) Message boards : Number crunching : Flakey AMD/ATI GPUs, including RX 5700 XT, Cross Validating, polluting the Database (Message 2023075)
Posted 14 Dec 2019 by Profile MagicEye
Post:
Is there any way to contact the project responsibles?
Are they aware of the problem?
Are there any solutions ongoing?

I have seen in the last days some tasks that were send out not only to 1 other host but to 2. On the one hand a very good idea.
On the other hand the 2 5700 GPUs still overruled the other 2 PCs. :(

The good thing is, that astropulse seems to run without error and really quite fast - about 1cr per second of run time. And with these tasks and in most cases also quite good AMD CPUs they get a lot of credits - maybe thats the reason they don't see that the 5700 card are producing so much waste.
8) Message boards : Number crunching : Flakey AMD/ATI GPUs, including RX 5700 XT, Cross Validating, polluting the Database (Message 2022817)
Posted 11 Dec 2019 by Profile MagicEye
Post:
I wrote to some people a private message - but didn't get any answer. :(
9) Message boards : Number crunching : SETI@Home will now cache 150 CPU work units and 150 per installed GPU (Message 2022816)
Posted 11 Dec 2019 by Profile MagicEye
Post:
More confirmation via GitHub:

Eric Korpela wrote:
I've dropped the GPU limit to 300 to keep us below 7M. We'll run it there
for a while.


What kind of "7M" does he mean?
10) Message boards : Number crunching : Welcome to the 20 Year Club! (Message 2020960)
Posted 28 Nov 2019 by Profile MagicEye
Post:
My anniversary is now more than 2 months in the past - but i didn't know about this thread until now.

The day of registration was random - but looking now on the date i'm happy about all these 9's ;)
(19.09.1999)
11) Message boards : Number crunching : Flakey AMD/ATI GPUs, including RX 5700 XT, Cross Validating, polluting the Database (Message 2020312)
Posted 23 Nov 2019 by Profile MagicEye
Post:
I check from time to time my invalid WUs.
Very often there are other PCs with e.g. RX5700 GPU, which compute about 50% errors.
As a wing man for my GPUs there are 2 different results for the WU and it is sent out to a third PC.
When the third user also has such a error-GPU, he will validate the wrong result and the good result is rejected.
I looked to this PCs and see about 50% error WUs.
But i am sure the other 50% have also errors.

Shouldn't it be better for the correctness of the results and for the science to block PCs with such high error rates?
Or send then not more then 2-3 WUs per day until the will send back about 90+% correct results?
12) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1997944)
Posted 12 Jun 2019 by Profile MagicEye
Post:
Up and crunching now under Ubuntu 18.04. Vega 56 and Radeon VII in the same system.

https://setiathome.berkeley.edu/show_host_detail.php?hostid=6993114


@Sean: I would like to know how your settings are for this PC?
Just the stock app and only 1 WU per GPU ?
13) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1997939)
Posted 12 Jun 2019 by Profile MagicEye
Post:
Also Windows/Lunatics is running fine with just 1 WU on the GPU for 24h without any error.
But switching to 2 WUs means that they hang after some minutes run time. But instead of timeout, the graphics driver is resetting.

My conclusion is: Seti@Home is running poor on the Radeon VII. I will continue to cruch this project on nvidia.
The VII is running perfect with Einstein and Milkyway.
14) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1997581)
Posted 9 Jun 2019 by Profile MagicEye
Post:
This weekend i had time to test again.
Now i have removed all optimizations, the txt-files are empty.
I also run only 1 WU on the GPU, the CPU-threads are still 10 used of 16.
And i still have WUs that stuck and go later in timeout.
Next step will be testing in Windows.
15) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995834)
Posted 29 May 2019 by Profile MagicEye
Post:

NoW i reduce the cpu used cores from 14 to 10.

There was a W missing.
16) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995823)
Posted 29 May 2019 by Profile MagicEye
Post:
Also without the cpu lock ohne WU is stucking. Its marked as active - not waiting or something like this. But there ist no progress and the fan slows down with just one really active WU.
In the meantime 3 other WUs were started and finished.
OK, at the weekend i read a little bit and try to understand, how to pin a GPU-program to a CPU-core.


I forgot you are running Linux.
IIRC this param is not working in Linux.

Stderr should give a notice....... Info: CPU affinity mask used: 1; system mask is ffff

Just to make sure reduce CPU tasks to 10 to see if this helps.


I thought the number of this WUs was reduced - but there is a time limit and i have a lot of them without notice, just found them in the list of my tasks.
The good thing is, they dont block the GPU for hours or days...

Here is the stderr of a "bad task":
[spoiler]
<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 4791.83 (3677746.15G/753.52G)</message>
<stderr_txt>
Maximum single buffer size set to:2048MB
Number of period iterations for PulseFind set to 1 
High-performance path selected. If GUI lags occur consider to remove -high_perf option from tuning line
SpikeFind FFT size threshold override set to:4096
TUNE: kernel 1 now has workgroup size of (64,1,4)
oclFFT global radix override set to:256
oclFFT local radix override set to:16
oclFFT max WG size override set to:256
oclFFT max local FFT size override set to:512
oclFFT number of local memory banks set to:64
oclFFT minimal memory coalesce width set to:64
OpenCL platform detected: Advanced Micro Devices, Inc.
Number of OpenCL devices found : 1 
BOINC assigns slot on device #0.
Info: BOINC provided OpenCL device ID used

Build features: SETI8 Non-graphics OpenCL USE_OPENCL_HD5xxx OCL_ZERO_COPY SIGNALS_ON_GPU OCL_CHIRP3 FFTW SSE2 64bit 
 System: Linux  x86_64  Kernel: 4.15.0-50-generic
 CPU   : AMD Ryzen 7 1700 Eight-Core Processor
 16 core(s), Speed :  3017.782 MHz
 L1 : 64 KB, Cache : 512 KB
 Features : FPU TSC PAE APIC MTRR MMX SSE  SSE2 HT PNI SSSE3 SSE4A SSE4_1 SSE4_2 AVX  AVX2  

OpenCL-kernels filename : MultiBeam_Kernels_r3584.cl 
ar=0.008117  NumCfft=116331  NumGauss=0  NumPulse=47020601216  NumTriplet=59991734432
Currently allocated 4121 MB for GPU buffers
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768
Linux optimized setiathome_v8 application
Version info: SSE2x (Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE2x Linux64 Build 3584 , Ported by : Raistmer, JDWhale, Urs Echternacht


OpenCL version by Raistmer, r3584

AMD HD5 version by Raistmer

Number of OpenCL platforms:				 1


 OpenCL Platform Name:					 AMD Accelerated Parallel Processing
Number of devices:				 1
  Max compute units:				 60
  Max work group size:				 256
  Max clock frequency:				 1802Mhz
  Max memory allocation:			 4244635648
  Cache type:					 Read/Write
  Cache line size:				 64
  Cache size:					 16384
  Global memory size:				 16978542592
  Constant buffer size:				 4244635648
  Max number of constant args:			 8
  Local memory type:				 Scratchpad
  Local memory size:				 65536
  Queue properties:				 
    Out-of-Order:				 No
  Profiling timer offset:			 1
  Global free memory:				 1
  SIMD per compute unit:			 4
  SIMD width:					 16
  SIMD instruction width:			 1
  Wavefront width:				 64
  Global mem channels:				 128
  Global mem channel banks:			 4
  Global mem channel bank width:		 256
  Local mem size per compute unit:		 65536
  Local mem banks:				 32
  Thread trace supported:			 Yes
  Board Name:					 AMD Radeon VII
  Name:						 gfx906
  Vendor:					 Advanced Micro Devices, Inc.
  Driver version:				 2841.4 (PAL,HSAIL)
  Version:					 OpenCL 2.0 AMD-APP (2841.4)
  Extensions:					 cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes 


Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.008117
Used GPU device parameters are:
	Number of compute units: 60
	Single buffer allocation size: 4048MB
	Total device global memory: 16192MB
	max WG size: 256
	local mem type: Real
	LotOfMem path: yes
	LowPerformanceGPU path: no
	HighPerformanceGPU path: yes
period_iterations_num=1

</stderr_txt>
]]>

[/spoiler]

No i reduce the cpu used cores from 14 to 10.
17) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995671)
Posted 28 May 2019 by Profile MagicEye
Post:
Also without the cpu lock ohne WU is stucking. Its marked as active - not waiting or something like this. But there ist no progress and the fan slows down with just one really active WU.
In the meantime 3 other WUs were started and finished.
OK, at the weekend i read a little bit and try to understand, how to pin a GPU-program to a CPU-core.
18) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995654)
Posted 28 May 2019 by Profile MagicEye
Post:
Thank you!
As a first quick solution i will remove this cpu lock.
19) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995645)
Posted 28 May 2019 by Profile MagicEye
Post:
I am not sure if i understand your question.

I use the parameter set from Mike above:
-sbs 2048 -period_iterations_num 10 -high_perf -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 -cpu_lock

I only changed the 10 iterations to 1 as mentioned.
I dont see n_instances_per_device there - so i think i dont use it.

The 2 WUs in parallel are managed by an app_config (0.5 GPU and 1CPU per WU)

What does the -cpu_lock do exactly?
20) Message boards : Number crunching : Radeon VII Seti performance vs 1080ti SoG? (Message 1995583)
Posted 28 May 2019 by Profile MagicEye
Post:
Radeon VII with 16GB.


Next 20


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.