This occurs about every 24~36 hours. I use school for 1 box that has an RX 6800 card and I need it to NOT get GPU Sep WUs. Once "school" disappears I get a load of these WUs and they all error out. I notice and re-create the school preferences. 24hrs later it's gone from the website.

Skip

Knock on wood I'm not seeing that problem, I setup the different venues years and years ago and they are still there and doing what they should do. One thought do you have Work setup as well? If not maybe that will make School stick for you.

This occurs about every 24~36 hours. I use school for 1 box that has an RX 6800 card and I need it to NOT get GPU Sep WUs. Once "school" disappears I get a load of these WUs and they all error out. I notice and re-create the school preferences. 24hrs later it's gone from the website.

Skip

Knock on wood I'm not seeing that problem, I setup the different venues years and years ago and they are still there and doing what they should do. One thought do you have Work setup as well? If not maybe that will make School stick for you.

<app_config>

 <app>
    <name>milkyway</name>
      <gpu_versions>
        <cpu_usage>0.5</cpu_usage>
        <gpu_usage>0.333</gpu_usage>
      </gpu_versions>
 </app>

</app_config>

http://man.opencl.org/deprecated.html

OpenCL Features Deprecated in OpenCL 2.0

clCreateCommandQueue


Error creating command queue (-6): CL_OUT_OF_HOST_MEMORY

		
						57	# of pending	
						78	# of .333s	
						36	# of .500s	
						114	total	

			Average all	209.32			no division applied
			Average 2x	83.99				
			Average 3x	82.34		1.655	3x secs avg advantage*
	
Notes:
Core temp almost rock steady @ 70C with new fan profile.
Slight throttling of the 2% OC Core Freq on 155w package limit on this Sapphire card.
Dropping to 1300MHz (Level 6) drops package to ~123w and 69C.
Pending count as of 4/5/2023 local.
*The 3x advantage seems to be growing very slightly over time.

Skip,

Keith is right. You should be able to run atleast 5 units on your RX 580. I think I am running 8 or 10 on mine and I only have 8 cpu cores and you have 16. Just depends on how long you want to limit your run time to. I just kept on increasing the number of units I was running until it was not that advantageous to run anymore.

Good Luck,

Allen

<app_config>
 <project_max_concurrent>10</project_max_concurrent>

 <app>
  <name>milkyway_nbody</name>
  <max_concurrent>4</max_concurrent>
   <app_version>
    <app_name>milkyway_nbody</app_name>
    <plan_class>mt</plan_class>
    <avg_ncpus>2</avg_ncpus>
    <cmdline>--nthreads 2</cmdline>
   </app_version>
 </app>

 <app>
  <name>milkyway</name>
  <gpu_versions>
   <gpu_usage>0.5</gpu_usage>
   <cpu_usage>0.5</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

As long as I'm begging...

Anybody want to share an app_config.xml for MW roughly appropriate for a 8 core CPU box with an AMD RX 580 card? I've next to no experience with these.

Again Thanx, Skip

This is the one I use:

<app_config>

<app>
<name>milkyway</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>
<app_version>
<app_name>milkyway_nbody</app_name>
<max_concurrent>5</max_concurrent>
<plan_class>mt</plan_class>
<avg_ncpus>2</avg_ncpus>
<cmdline>--nthreads 2</cmdline>
</app_version>
</app_config>

I do delete the top section if I'm not running gpu tasks. The top gpu part tells your pc to run 2 gpu tasks at the same time while the bottom cpu part says to run 5 tasks at one time each using 2 cpu cores.

client_state.xml

Yes, the MW Separation app is rather poorly optimized. It won't use very much of the gpu at all at any time. It begs running at least 2X on the card to get the gpu utilization up closer to 90%. 2X for Nvidia cards is about max becase of how the Nvidia drivers have to virtualize their OpenCL component to run the Separation app.

AMD or ATI cards OTOH, typically can run at least 4X or maybe 5X depending on how much memory the card has. The app doesn't really use all that much memory. I don't have any running currently to tell you exactly how much the app uses. I remember its about 1.6GB I think but don't quote me.

<app>
<name>einsteinbinary_BRP7</name>
<user_friendly_name>Binary Radio Pulsar Search (MeerKAT)</user_friendly_name>

<gpu_versions>
<cpu_usage>1.0</cpu_usage>
<gpu_usage>0.5</gpu_usage>
</gpu_versions>
</app>

IIRC the solution is to run more than one task concurrently with app_config.xml file.

<app_config>
 <app>
  <name>milkyway_nbody</name>
  <max_concurrent>3</max_concurrent>
 </app>
 <app_version>
  <app_name>milkyway_nbody</app_name>
  <plan_class>mt</plan_class>
  <avg_ncpus>4.0</avg_ncpus>
  <cmdline>--nthreads 4</cmdline>
 </app_version>
</app_config>

This will run 3 n-Body tasks with each 4 threads on a 12 core CPU. If that isn't enough, you can try "--nthreads 5" without changing anything else, but you'll have to see, if that really improves the throughput. Don't do it, if the CPU also needs to feed a GPU.

I converted one of my XP64 machines over to Ubuntu v10.04 to try DNETC on the ATI card and it works... but I had to use the Berkeley variant install instead of the Debian/Ubuntu package due to a permissions bug in x64 package with ATI driver... it's an open bug on launchpad I was trying to narrow down but it's beyond my ability to pursue further till I get some help from the package devs.

Is there a possibility to test a linux 32 or 64 bit gpu client app for this project ?
I have an Ati Radeon HD5870 which crunch on Dnetc.
I would prefer to crunch on Milkyway@Home if a linux gpu app has been provided with.

Thanx much... this explains what I'd thought to be an oddity between two 4850 equipped machines (one has ram clock that will not go below 993 in ccc, other has been running with VRAM clock at 650, both with GPU clock at ~650).

UPDATE: I guess I expected a couple seconds difference not a couple MINUTES!

On a AMD 9850, windozeXP machine w/ 2GB RAM with 4850 (1GB) I took the timings from it running last night at the lower vram clock (forgot I'd set it down from 650 to 475 yesterday). I then ran about 5 MW WUs and 5 Collatz WUs with the higher vram clock setting.

850 core/475 vram vs 850/950.

MW no measurable difference.

Collatz avg 19min 44secs vs 16min 52secs!!