Bitsum Community Forum

General Category => Process Lasso => Topic started by: BobRoss on January 09, 2019, 01:47:21 PM

Title: How to optimize for BOINC? Work units are all named the same thing
Post by: BobRoss on January 09, 2019, 01:47:21 PM
I run BOINC and mostly the PrimeGrid sub-project.  The problem is; all the work unit processes are named the same thing.  For instance primegrid_cllr.exe.  When the work unit is done, it fetches another one.  My question is - How can I keep work units on their own cores if they are all named the same and new ones start at random?  Is that even possible?  I can do this manually via task manager by setting affinity but that is a huge pain.

Thank you for any help.
Title: Re: How to optimize for BOINC? Work units are all named the same thing
Post by: Jeremy Collake on January 09, 2019, 02:03:48 PM
The assignment of unique persistent CPU affinities to multiple instances of the same application is a feature under development. At this time, my only guidance is to wait for this. I do not have an ETA.
Title: Re: How to optimize for BOINC? Work units are all named the same thing
Post by: BobRoss on January 09, 2019, 02:39:44 PM
Thank you for the reply!  I look forward to this feature! 

Cheers,
Bob
Title: Re: How to optimize for BOINC? Work units are all named the same thing
Post by: Jeremy Collake on May 12, 2019, 04:48:31 PM
This feature was finally added BTW, see the 'Instance Balancer': https://bitsum.com/product-update/processlasso-v901/
Title: Re: How to optimize for BOINC? Work units are all named the same thing
Post by: Jeremy Collake on May 16, 2019, 02:30:17 PM
As of Process Lasso v9.1.0.29 BETA, wildcards and 'chilof: processname' rules are allowed in the Instance Balancer.

That means that to cover *all* Boinc tasks, including those from multiple projects, you would use a rule with a match of:

childof: boinc.exe

See attached screenshot for example config.