Could the project admins set the project to tell it there is no gpu apps available please. From memory Dr Anderson posted in one of the mailing lists (boinc_dev or boinc_alpha) the xml that needed to be set (possibly config.xml) so that the clients get told there is no nvidia gpu support. This will stop the client asking for work they can never get.

I ask because my client has just wasted a scheduler request asking for nvidia gpu work when the project doesn't support them and now has been backed off an hour before it can ask again, probably to ask for more gpu work and get backed off for another hour.

---

BOINC blog

I don't think that the server version is sufficiently up to date for the "no gpu" code.

CC_config can apparently be set on user's computers to do the same thing.

And there's no work anyway, as you can see by looking at the blue menu to the left, 5th from the bottom.

---

Backups: Here

Les Bayliss wrote:

<quote>
CC_config can apparently be set on user's computers to do the same thing.
</quote>

Hi Les,

I don't know how to do this.
Could you kindly post instruction on how I can do this ?

Thanks in advance
Byron

The wiki page is here. Scroll down to 'exclude_gpu'.

The wiki page is here. Scroll down to 'exclude_gpu'.

ah ... OK thank you Iain.

I don't think that the server version is sufficiently up to date for the "no gpu" code.

CC_config can apparently be set on user's computers to do the same thing.

Unfortunately in v6.12.xx and earlier clients, users can't disable individual projects from using GPU's, the available cc_config-options will disable GPU's for all projects. Seeing that MarkJ runs GPUGRID and Byron runs SETI@home, neither of them would want to disable GPU-crunching on their computers.

Disabling GPU-crunching for individual projects is an option in v6.13.x, but these clients is alpha-clients with many rough edges, so for anyone not being alpha-testers it's recommended to stay away from these clients for now. Atleast from the look of things, GPUGRID doesn't currently work with v6.13.x-clients, since it's one of the many projects that haven't disabled upload-certificates yet.

Seeing that MarkJ runs GPUGRID and Byron runs SETI@home, neither of them would want to disable GPU-crunching on their computers.

thank you Ingleside. I did not know that. I think I will not Disabling my GPU-crunching on my BOINC client 6.12.34

I don't think that the server version is sufficiently up to date for the "no gpu" code.

Are there any plans to update the server version? Just a little job for Jonathan to look into :-)

I did manage to get a resend of a hadcm3n eventually, after many wasted attempts asking for GPU work.

---

BOINC blog

Upgrading the server version is a very big job, because this project needs a highly customised version.
This customising needs to be done each time there's an upgrade.

The last time it was tried, it had to be abandoned, because a lot of the code failed to work.

---

Backups: Here

We are currently using the BOINC server_stable version, and we don't plan to upgrade again for some months (at least 2012).

As was mentioned, we have to compile in extra options when building the software, so we need to test that it will work before we deploy it on the live site. The last upgrade was done after a server crash; I am somewhat greyer than I was, and less than keen to repeat the experience :-)

However, we do have a roadmap of work that needs to be done to our system, and updating BOINC is definitely on there for next year.

Jonathan

---

Upgrading the server version is a very big job, because this project needs a highly customised version.
This customising needs to be done each time there's an upgrade.

The last time it was tried, it had to be abandoned, because a lot of the code failed to work.

I was being sarcastic when I said it, hence the smiley.

I understand that its something most projects don't like doing as something always breaks during the upgrade process. In fact I haven't heard of any project that has managed to upgrade without problems.

I did ask Dr Anderson if he could repeat the xml he posted, just in case the cpdn server is up to date enough to use it. Your server is reporting its version 611.