My rig seems to be quite stable with the new software. For anyone interested or in need of an app_config.xml, mine is as follows, for AMD of course..

<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.08</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
</app_config>

If anyone sees a problem with this, please let me know.

Happy crunching!!

Edit: HHmmmm.... The GPU tasks are not nearly taxing my hardware. Estimated time 1:35, real time approximately 1:45, with the above app_config.

Any ideas?

---

DOn't forget that new BOINCs go on extended backup times if they can't get tasks. they max out at 24h - so it will be a while before all the unattended machines are back crunching.

Thanks, yeah I did forget about that..

But now for a weird problem, It finally downloaded some new cudas... 22!!

what the....

Yeah I aborted all those as I set cuda 50 as the default, don't know why it did that. Will have to wait and see if it sends me the correct cudas.

My rig seems to be quite stable with the new software. For anyone interested or in need of an app_config.xml, mine is as follows, for AMD of course..

<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.08</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
</app_config>

If anyone sees a problem with this, please let me know.

Happy crunching!!

Edit: HHmmmm.... The GPU tasks are not nearly taxing my hardware. Estimated time 1:35, real time approximately 1:45, with the above app_config.

Any ideas?

I think things need to settle down a bit... I have a pretty good load on my GPUs now, but that is at 4X4 with the new Crimson drivers. My efficiency may be suffering, I can't be sure though....

---

My rig has gotten a bit messy also. Performed a clean install of CCC 15.1 a few minutes ago. I'll let that settle in. Otherwise, I have reviewed all of my settings. They seem to be in line.

My tasks:

State: All (1544) · In progress (503) · Validation pending (397) · Validation inconclusive (268) · Valid (178) · Invalid (188) · Error (10)
Application: All (1544) · AstroPulse v7 (6) · SETI@home v7 (166) · SETI@home v8 (1372)

---

My rig has gotten a bit messy also. Performed a clean install of CCC 15.1 a few minutes ago. I'll let that settle in. Otherwise, I have reviewed all of my settings. They seem to be in line.

My tasks:

State: All (1544) · In progress (503) · Validation pending (397) · Validation inconclusive (268) · Valid (178) · Invalid (188) · Error (10)
Application: All (1544) · AstroPulse v7 (6) · SETI@home v7 (166) · SETI@home v8 (1372)

All right, tired of playing with it. I performed a clean install of the "latest greatest" CCC and everything seems to be o.k. I was getting driver restarts. They seem to have stopped. I'll let it sit for the weekend. Not gonna push it.

---

I am trashing a lot of units it seems... Why so many invalids? Any suggestions?

---

Dont change that much all the time.
Let it run some time.

---

With each crime and every kindness we birth our future.

Well, it seemed to have started yesterday at about 12.00 UTC (whatever it is at your place).

Is there any reason why it would be impossible to run two GPU iterations at one time when you only have two cores in your CPU?

I tried and one of the cores shutdown.

Thanks!

UPDATE: Seems like even on my quad it wants to stop the cpu cores when I run more than one gpu iteration.

---

From what I can tell, maybe depends on the application you're refferring to, and what you're doing on your CPU

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I'm really not doing anything except SETI as far as real work. I do have the browser open, but not much going on there.

Maybe something odd about the config file. I copied it off here and it looked good.....what do I know. *;)

---

Clarifying, From your hosts, I can see a mix of nVidia GPU equipped hosts, and AMD hosts ? Which ones ? All of them ?

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Sorry for the poor information giving. It only on my two nVidia machines. As soon as I dumped the config files and restarted with only one iteration of gpu work, everything returned to normal. I wonder if there is something wrong with the config file. This is the one I used.....

<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>

---

You might be pushing those processors a little hard IMO. Try backing off number of instances. If they then appear to work fine, then you need more feeding capacity.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Sorry for the poor information giving. It only on my two nVidia machines. As soon as I dumped the config files and restarted with only one iteration of gpu work, everything returned to normal. I wonder if there is something wrong with the config file. This is the one I used.....

<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>

I think your problem is the "<max_concurrent>2</max_concurrent>". I believe that tells BOINC that only 2 total instances of all setiathome_v8 tasks can run, regardless of whether they're GPU or CPU. I'd recommend removing that line altogether.

---

Are you saying that you can call for less than a full iteration of gpu at one time, rather than 1,2,3,4.... you can actually call for 1.5, 1.6 etc.?

---

Sorry for the poor information giving. It only on my two nVidia machines. As soon as I dumped the config files and restarted with only one iteration of gpu work, everything returned to normal. I wonder if there is something wrong with the config file. This is the one I used.....

<app_config>
<app>
<name>astropulse_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.5</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>

I think your problem is the "<max_concurrent>2</max_concurrent>". I believe that tells BOINC that only 2 total instances of all setiathome_v8 tasks can run, regardless of whether they're GPU or CPU. I'd recommend removing that line altogether.

Then what indicates how many instances you wish to run? I thought that was it.

---

You might be pushing those processors a little hard IMO. Try backing off number of instances. If they then appear to work fine, then you need more feeding capacity.

I'd suggest trying the GTX 650Ti in the Core 2 Quad & the GT730 in the Athlon.
My E6600 Core 2 Duo has no problems keeping 2*GTX 750Tis fed running 2 MB WUs at a time.
Generally, a the more powerful the GPU the more powerful the CPU required to keep it fed.

If running AP work, then others will need to advise the minimum requirements; but from what I've read it's often one CPU core per GPU.

---

Grant
Darwin NT

Then what indicates how many instances you wish to run? I thought that was it.

<gpu_usage>0.5</gpu_usage> = 2 WUs per GPU.
<gpu_usage>0.3</gpu_usage> = 3 WUs per GPU.
<gpu_usage>1.0</gpu_usage> = 1 WU per GPU.

---

Grant
Darwin NT

I've never cared for putting that max concurrent right there.

<app_config>
<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.40</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v8</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.40</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.40</cpu_usage>
</gpu_versions>
</app>
</app_config>

This should give you 1 work unit per GPU.

AMD need more CPU than Intel, at least in my opinion.

Looking at the 2 nvidia machines, can you swap the GPUs?

You might be able to get better result with the 730 in the dual core and the 650Ti in the 4 cores.

Then you might be able to increase the number of work units on that 650Ti.

Or is it a power issues on those machines?

Edit...

Had to insert missing </app_config> at the end