I would like to be able to tell my client:...

Already available with the latest clients (6.10.36 and above), set resource share of the project you want to fetch one task from to zero. This requires that the project update their server software to at least changeset [trac]changeset:21134[/trac]. Without that update the project will not honor this setting!

I would like to be able to tell my client:...

Already available with the latest clients (6.10.36 and above), set resource share of the project you want to fetch one task from to zero. This requires that the project update their server software to at least changeset [trac]changeset:21134[/trac]. Without that update the project will not honor this setting!

Ah well it would be nice to have more control then that and have it built in to the client not the server.

I would like to be able to tell my client:...

Already available with the latest clients (6.10.36 and above), set resource share of the project you want to fetch one task from to zero. This requires that the project update their server software to at least changeset [trac]changeset:21134[/trac]. Without that update the project will not honor this setting!

Ah well it would be nice to have more control then that and have it built in to the client not the server.

Moving that feature so it's built into the client would need server changes, so you're back at square one.

---

Ah well it would be nice to have more control then that and have it built in to the client not the server.

It is already built into the newer clients. It's just that not all projects have updated their server code that supports this move.

I would very much like the option to prioritize the CPU (and GPU) workload. For example. If i leave my computer untouched for a minute, it will switch to full processorusage, or what ever i set it to, but then when i start to use my computer, it will slow down to about 50% or 25% usage.

+1 to this here.

I'd really love to be able to tell my computer to use 25% of its power (one of the 4 CPUs, say, or all 4 CPUs at 25% workload) when the computer's not idle, and 100% when it is idle.

Additionally, if I could (for example) tell it to use one GPU when the computer is not idle, and all GPUs when it is idle, that'd be fantastic too.

+1

This perfectly sums up my wishes.

+1 from me, too.

If it helps to clarify, essentially the request is take the current settings for:
% of Processors
% of CPU Time
and split them in to two settings, one for when the computer is idle and one for when it is not (similar to how the Memory Usage parameter is currently handled).

Then, add similar parameters for:
% of GPU Processors
% of GPU Time
and allow them to also have different values for when the computer is idle and when it is not.

Cheers,

- Nathan

Until both GPU manufacturers add GPU throttle controls to their drivers, there is nothing that the BOINC developers can do about this. The GPU can only be used completely (all stream processors do CUDA or CAL work), or not (all stream processors are idle).

Until both GPU manufacturers add GPU throttle controls to their drivers, there is nothing that the BOINC developers can do about this. The GPU can only be used completely (all stream processors do CUDA or CAL work), or not (all stream processors are idle).

That's ok.

Until then, I assume "in use" / "not in use" CPU settings would be technically feasible?

Until then, I assume "in use" / "not in use" CPU settings would be technically feasible?

I asked the developers, but they don't see the need for it now that BOINC has the CPU Usage percentage, with which you can tell BOINC to suspend doing work as soon as any non-BOINC applications takes up the amount of CPU cycles set in this preference.

I'd like some more internet connection flexibility.

Like the 'different proxy settings' request, I alternate between work and home settings: large bandwidth at work, small bandwidth (and quota) at home.

So it would be nice to set a project to network/no network separately from the general preferences.
This could be used e.g. for SETI, turning off network for SETI only for the half-week downtimes keeping other running projects connected. Or for allowing network to projects with small filesizes on limited internet, while keeping large up/downloads to the high accessibility times.

By default, BOINC uses the following setting: "When processor usage is less than 25%."

Well, I think that leaving this setting at 25% is a several mistake, because all new users that don't know well BOINC, will leave it as is. If you don't modify this setting, BOINC will not work a lot, because it's very common to have a processor usage more than 25%

If you don't modify this setting, BOINC will not work a lot, because it's very common to have a processor usage more than 25%

This value is for all non-BOINC programs that actively use the CPU and it's for all those (new) users who find that just running BOINC without that value is slowing their system down.

BOINC is also using by default to not do work when the user is active, while this preference will make sure their AV scan or back-up or whatever else is running at periodical times will be able to finish without too much trouble.

So it would be nice to set a project to network/no network separately from the general preferences.
This could be used e.g. for SETI, turning off network for SETI only for the half-week downtimes keeping other running projects connected.

As soon as you set something on a project's preferences page, it must be set for that project only. When using the general preferences, it's global, for all projects you're attached to.

Are you're asking for project specific network limitations, and be able to set that through that project's preferences page?

So it would be nice to set a project to network/no network separately from the general preferences.
This could be used e.g. for SETI, turning off network for SETI only for the half-week downtimes keeping other running projects connected.

As soon as you set something on a project's preferences page, it must be set for that project only. When using the general preferences, it's global, for all projects you're attached to.

Are you're asking for project specific network limitations, and be able to set that through that project's preferences page?

I was rather thinking of a network/no network button, like NNT.

Project specific network limitations on a preference page would probably work just as well, but might present problems when using local preferences. I've got those in place, since you can set a network timeslot on the web, but day-by-day override is only available locally.

I like it, so forwarded that to the developers. :)

Hello,

I want to know if you could add my wish in your list.
I would like that you configure or create a hotkey to set the boinc agent in standly/snooze mode.
I want to avoid to use the menu (by click) in the taskbar.

I prefere hotkey click Ctrl + L than Ctrl + Alt + Supp + Lock Computer.

Thank you.

Are you're asking for project specific network limitations, and be able to set that through that project's preferences page?

I was rather thinking of a network/no network button, like NNT.

Project specific network limitations on a preference page would probably work just as well, but might present problems when using local preferences. I've got those in place, since you can set a network timeslot on the web, but day-by-day override is only available locally.

This was requested in Trac three years ago, as #139. There are even contributed patches adding the feature, but they were never applied to the official version.

---

Also forwarded to the developers. :)

Hello,

I want to know if you could add my wish in your list.
I would like that you configure or create a hotkey to set the boinc agent in standly/snooze mode.
I want to avoid to use the menu (by click) in the taskbar.

I prefere hotkey click Ctrl + L than Ctrl + Alt + Supp + Lock Computer.

Thank you.

The developers added it to their to-do list. See for progress Trac ticket [trac]#1001[/trac].

I was rather thinking of a network/no network button, like NNT.

Project specific network limitations on a preference page would probably work just as well, but might present problems when using local preferences. I've got those in place, since you can set a network timeslot on the web, but day-by-day override is only available locally.

Sorry, I fought for it, but it isn't going to happen again this time.
The project wide back-off on uploads and downloads will be increased though. At this time it has a maximum of 4 hours, while (each backoff is multiplied by a random number 0..1, so the max average of 2 hours.

This will now be increased to possibly 12 hours, perhaps more, with what I hope is a project wide back-off that eventually stays at its maximum value, not resets itself to the wildest of variations as it does now.

I was rather thinking of a network/no network button, like NNT.

Project specific network limitations on a preference page would probably work just as well, but might present problems when using local preferences. I've got those in place, since you can set a network timeslot on the web, but day-by-day override is only available locally.

Hello Carola - fancy meeting you here!

As it happens, this has already been worked on - see trac [trac]#139[/trac]. Milo (CPDN admin) was running out of disk space, and needed to specify / finance / order / take delivery / install / configure a new server (and you know how long that takes!) before he could accept another upload. At the time, the upload delay limit was just 14 days, after which the science was just thrown down the tubes by BOINC. So Thyme Lawn wrote all the code needed, and I tested it for him prior to submission - on the 6.6 codebase, so it works well enough with CUDA - not fully updated for ATI, but IIRC that doesn't matter for you. I'll still have the test downloads available somewhere, if you're interested - I'm sure TL wouldn't mind.

But, as usual, even with fully developed code patches, it still got a "not invented here" response from David - he just upped the time limit, as he has again this time.