I just switched from Folding back to seti for the WOW event and thought I had all the bases covered. But I think I have an issue with GPU load.

I have two R9 290s (Hawaii), one MSI 977MHz, and the other a Sapphire 1000 MHz , on a 990FX Extreme 4 motherboard with FX-8350 cpu

win 7 sp 1 32-bit

catalyst package 15.7.1

driver ver. 15.200.1062.0

Boinc manager ver 7.4.42

lunatics app v43b

I have assigned 1 cpu per GPU wu and running 2 wu per card

Temps on card 0 are 65 C and on card 1 are 55 C.

GPU core clock and Mem clock are stock and smooth. The GPU load is literally jumping from 0 to 100% and I have run out of things to try to get it smoothed out.
SIV has me at 65% cpu utilization.

I do not remember it acting this way last year. Anyone with an idea of what I am overlooking?
Thanks
Pokey

---

GPU core clock and Mem clock are stock and smooth. The GPU load is literally jumping from 0 to 100% and I have run out of things to try to get it smoothed out.

Is that while crunching AP (Astro Pulse) or MB (MultiBeam), or both types of WUs?

---

Grant
Darwin NT

MultiBeam (setiathome v7 7.03)

---

MultiBeam (setiathome v7 7.03)

Shouldn't that be 7.07 ?

http://setiathome.berkeley.edu//apps.php

Not that it has anything to do with the GPU load.

---

I double checked and it is V7 7.03 (opencl_ati5_cat132).

I agree that's a little strange.

---

What version of Lunatics are you running? Current version is v43b

---

I'm not sure if you can get away with running multiple wu per gpu on that card. I would get more invalids so I went back to just one wu per gpu. If you have crossfire on, turning it off might help. I think the main problem is that some of the mb work units going out have been longer running as well as having lower gpu utilization. So if I'm not crunching ap my rac takes a huge hit. The -sbs 256 switch might help, and the new readme file has some other new switches you can try as well.

Zalster: I'm using v43b. In fact I installed it trying to solve this issue.

woohoo: I ran multiple WUs last year. I'll look into some of these ideas tomorrow when I am a little fresher.

I will check back in then.

---

i dunno ati infuriates me with their drivers .
i am trying to get the drivers installed so i can use the streaming procesors in a HD 4290 and for the life of me i cannot get the drivers installed in win 10 and it keeps saying no usable gpu found but it is there boinc recohnizes is

---

I came down with a bad case of i don't give a crap

i think the 4290 requires an older driver that you can't install under windows 10

fwiw i've also had problems with invalid results at einstein running multiple wu per gpu. it could be a driver issue, but i tend to always choose the latest drivers. with two of my machines on windows 10 i don't even have the option of using last year's drivers.

Look for a file called mb_cmdline_win_x86_SSE2_OpenCL_ATi_HD5.txt and add the following.

-sbs 256 -tune 1 64 4 1 -tune 2 64 4 1 -oclFFT_plan 256 16 256 -cpu_lock.

This should speed up your GPU`s.

Also try to run 3 instances on the cards.

Make sure you reserve at least one CPU core for each card otherwise your cards can`t be feeded properly.
I`d suggest to set CPU to 50% in Boinc so you have 4 cores free.
Thats how i`m running it to have plenty of ressources.

---

With each crime and every kindness we birth our future.

i am trying to get the drivers installed so i can use the streaming procesors in a HD 4290 and for the life of me i cannot get the drivers installed in win 10 and it keeps saying no usable gpu found but it is there boinc recohnizes is

Aside from the possible Windows 10 incompatibility, I wouldn't blame the drivers. I would guess that old chipset graphics like HD 4290 simply doesn't support OpenCL, which is what BOINC would be looking for. OpenCL on discrete HD 4000 GPUs was only at a beta level and I know from past experience that it wasn't great at working with BOINC. It's possible that you could get some CAL driver support recognised in BOINC, but that really isn't very useful in S@h.

---

Soli Deo Gloria

i am trying to get the drivers installed so i can use the streaming procesors in a HD 4290 and for the life of me i cannot get the drivers installed in win 10 and it keeps saying no usable gpu found but it is there boinc recohnizes is

Aside from the possible Windows 10 incompatibility, I wouldn't blame the drivers. I would guess that old chipset graphics like HD 4290 simply doesn't support OpenCL, which is what BOINC would be looking for. OpenCL on discrete HD 4000 GPUs was only at a beta level and I know from past experience that it wasn't great at working with BOINC. It's possible that you could get some CAL driver support recognised in BOINC, but that really isn't very useful in S@h.

WEll that explains that hehe i guess i have to get 2 750 ti

---

I came down with a bad case of i don't give a crap

OK I am back.

I did go back and set 3 WUs per. Here is my app_config:

<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.333</gpu_usage>
<cpu_usage>.50</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config>

I also noticed that I have attracted an astropulse wu which is muddying the waters a bit. I have an astropulse and a MB on the same card.

I am using siv32x and it looks like cpu-0 is getting loaded up......lots of red on that one graph. All the other cpus are green. Usage is hanging around 75% overall.

Mike: I have not done your cmd line yet. What does it do?

---

i am trying to get the drivers installed so i can use the streaming procesors in a HD 4290 and for the life of me i cannot get the drivers installed in win 10 and it keeps saying no usable gpu found but it is there boinc recohnizes is

Aside from the possible Windows 10 incompatibility, I wouldn't blame the drivers. I would guess that old chipset graphics like HD 4290 simply doesn't support OpenCL, which is what BOINC would be looking for. OpenCL on discrete HD 4000 GPUs was only at a beta level and I know from past experience that it wasn't great at working with BOINC. It's possible that you could get some CAL driver support recognised in BOINC, but that really isn't very useful in S@h.

Not all Radeon HD 4000 series GPUs even had beta level OpenCL support. However I've had no issues with my older HD 3450's & Windows 10 using the same ancient Cat 12 driver I use in Windows 7. They are happy to run projects that support CAL just fine.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

i am trying to get the drivers installed so i can use the streaming procesors in a HD 4290 and for the life of me i cannot get the drivers installed in win 10 and it keeps saying no usable gpu found but it is there boinc recohnizes is

Aside from the possible Windows 10 incompatibility, I wouldn't blame the drivers. I would guess that old chipset graphics like HD 4290 simply doesn't support OpenCL, which is what BOINC would be looking for. OpenCL on discrete HD 4000 GPUs was only at a beta level and I know from past experience that it wasn't great at working with BOINC. It's possible that you could get some CAL driver support recognised in BOINC, but that really isn't very useful in S@h.

Not all Radeon HD 4000 series GPUs even had beta level OpenCL support. However I've had no issues with my older HD 3450's & Windows 10 using the same ancient Cat 12 driver I use in Windows 7. They are happy to run projects that support CAL just fine.

Well The video card states that it supports OpenCL 1.0
I'm reluctant to try it again since the last attempt resulted in 160+ aborts

---

I came down with a bad case of i don't give a crap

OK I am back.

I did go back and set 3 WUs per. Here is my app_config:

<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.333</gpu_usage>
<cpu_usage>.50</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config>

I also noticed that I have attracted an astropulse wu which is muddying the waters a bit. I have an astropulse and a MB on the same card.

I am using siv32x and it looks like cpu-0 is getting loaded up......lots of red on that one graph. All the other cpus are green. Usage is hanging around 75% overall.

Mike: I have not done your cmd line yet. What does it do?

sbs increasing single buffer size so it uses bigger kernels.
The other switches optimising such kernels further more.

---

With each crime and every kindness we birth our future.

OK I am back.

I did go back and set 3 WUs per. Here is my app_config:

<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.333</gpu_usage>
<cpu_usage>.50</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
</app_config>

I also noticed that I have attracted an astropulse wu which is muddying the waters a bit. I have an astropulse and a MB on the same card.

I am using siv32x and it looks like cpu-0 is getting loaded up......lots of red on that one graph. All the other cpus are green. Usage is hanging around 75% overall.

Mike: I have not done your cmd line yet. What does it do?

sbs increasing single buffer size so it uses bigger kernels.
The other switches optimising such kernels further more.

I am using the following app_config.xml. With some adjustments you can change the number of concurrent WUs and the percentage of CPU/GPU used. More info can be found under the AMD CPU Tips htread, it is at least a couple of weeks old though. Good luck!

<?xml version="1.0"?>

-<app_config>


-<app>

<name>astropulse_v7</name>

<max_concurrent>5</max_concurrent>


-<gpu_versions>

<gpu_usage>.5</gpu_usage>

<cpu_usage>.33</cpu_usage>

</gpu_versions>

</app>


-<app>

<name>setiathome_v7</name>

<max_concurrent>5</max_concurrent>


-<gpu_versions>

<gpu_usage>0.5</gpu_usage>

<cpu_usage>0.33</cpu_usage>

</gpu_versions>

</app>

</app_config>

---

Louis - your app_congig.xml is WRONG.
You have used an "XML sensitive" editor and it has introduced the following errors:

<?xml version="1.0"?>

is NOT used by the parser within BOINC

All lines starting with

-<

MUST start with "<"

When editing the ".xml" files used by BOINC (and SETI@Home) you MUST use a plain text editor like Windows Notepad, and make sure you save them with the correct ".xml" extension, otherwise there can be no guarantee they will work correctly.

The file posted by Pokey is correct, and will run:
3 MBs at a time, each with 0.5 CPU core set aside
or
2 APs at a time, each with 1 CPU core set aside

---

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