Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#295 closed Enhancement (wontfix)

Per application or project settable affinity of CPUs.

Reported by: Ageless Owned by: davea
Priority: Minor Milestone: Undetermined
Component: Client - Daemon Version:
Keywords: Cc: dbraun@…

Description

As posted by David Braun on Predictor Alpha:

I think it would be nice to have a per project or per application preferences such as "use at most N cores for application/project blah", or maybe "when application blah is active use at most N cores.

Change History (4)

comment:1 Changed 17 years ago by Nicolas

Note this isn't "affinity" in the sense of locking a process to a single CPU (see #15 and #325 for that).

comment:2 Changed 17 years ago by ohiomike

I agree, being able to set project a to x CPU's and project b to y CPU's would make project management easier for the user. The percentage is squirrelly to use at best (with 4 projects running, you have to change preferences in 4 different places to set project x to 50% of the load and the other 3 to 16% each. And then Boinc ignores you anyway).

comment:3 Changed 17 years ago by davea

Resolution: wontfix
Status: newclosed

What problem does this proposal address? Resource shares (which can be managed centrally with an account manager) do in fact work.

comment:4 Changed 17 years ago by Didactylos

ohiomike, projects weights are NOT percentages. If the weights of your four projects are all at the default 100, then to achieve the weighting you describe, set project X to 300. The client then works out the percentages for you.

Note: See TracTickets for help on using tickets.