Hello, i am fairly new to grid computing, therefore only just brought only one of my PC's into it. What i find is: I cannot really control my cpu-time donation. the percentagea associated with the projects (in BAM) do not get reflected nor in actual cpu usage nor in overall usage. furthermore, one of the projects constantly prioritises its tasks over any other project, thus forcing to me to manually halt execution. after completing my tasks therein, i decided to withdraw from that project through BAMstats, which i was using. But, even after trying to refresh the configuration state locally, the project keeps on loading tasks on to my PC anyway.
I am so angry now, that i am close to deinstalling all that software and not using it on any PC anymore. I feel my willingness to contribute is getting misused, or by badly written schedule-management software, or by bad behavior from one specific project (btw, i am speaking of NFS@home), i cant tell, what exactly is going on.
Can anybody enlighten me, about the things i could do INSTEAD of simply withdrawing my contribution?

First off all: Thank you very much for answering in such understanding and informative way. It help a lot to learn, that i am not the only one with those issues. For now, i am still evaluating my participation with this/theese project(s), of course appreciating my freedom to choose projects to which i may spend my CPU resources.

I was aware of the relative weighting value and how it converts to %. But thanks anyway.

After reading your reply, i changed the switch time to a much shorter value, as i wasnt caring about that yet.

Nice to remind me of the potential value of volunteer computing. Lets hope, those expectations will hold true. There are still some doubts on this, as legitimacy of project computing requests isnt yet transparent to me.

Finally, i started without BAM, but then realised, that would lead to managing multiple PC's separately in the future. Therefore i started investigating that piece of management software a week ago, to learn, how my machine(s) would behave.

In doing so, i lost the ability to withdraw from that one project from the client. So i did it in BAM, when it said, that change would propagate to my machine. But it still didnt do so. For now i halted that project by hand on the client, something i'd prefer to not have to do, as synchronising with BAM should really hold its promise.

To read your post was kinda relief for me, and it motivated me indeed to keep trying...

Also, i like the wording "... some that are plain aggro in pushing themselves in front", as it puts words to what my feeling was about that project.

Thanks again and best of ...

Ok, just want to say: problem resolved. I dont know why, but apparently the following behavior got me rid of the undesired project:

- the project was already withdrawn frm BAM
- i quit BAM from inside the client
- then withdrew from the project once more
- then reconnected to BAM
- finally restarted the boinc service

Now, everything works fine again :-)