The Scottish Boinc Team

Oh !!! The group is an entry field too. I never twigged to that. That will be handy, thanks.

I'll press ahead anyhow as I am hoping to extend it to cover things which boinctasks can't do (at least what I think it can't do)

Limit the number computers in a group to no more than 20. If you collapse the group, I think it helps response time.

Made groups and still seem to be getting heaps of problems when I bunker up.

Maybe my laptop isn't up to the job? Dell Vostro 1720, Core2 processor P8600, 4Gb RAM, Windows 7 64bit

Glad I'm not the only one

Is it possible to have multiple copies of Boinctasks running on the same machine please? If so, I'd simply split my client machines into groups across 2 or more instances of boinctasks

scole of TSBT wrote: ↑Sun Mar 17, 2019 7:59 pm Try a manual method. Stop the boinc client, delete the account and master xml files for that project, go to project dir and delete the dir for those projects, restart the boinc client.

Sussed it. This did the trick.

BTW, I had 240 boinc clients setup on BoincTasks for the XANSONS work release. No matter how I sliced it, it had my CPU utilization at 100%. Had to shut it down, open it only to check on things, then shut it down again.

Maybe you guys just have too many systems ......... not that that is a bad thing. Copes with my meager croft fine with a few cores dedicated on an old xeon server. Guess it wasn't designed to run entire server rooms ( I'm just jealous )

Can't have too many systems (need some shares in electricity companies).

Too many clients and too many WU soon causes problems for me though as I get the impression that boinctasks is keeping microscopic detail on every WU. Admirable motives but overkill in a lot of situations. Seems it creates its own DDOS attack on itself