crucial value for resource management

Message boards : Questions and problems : crucial value for resource management
Message board moderation

To post messages, you must log in.

AuthorMessage
Robsanium

Send message
Joined: 19 Jul 21
Posts: 2
Message 104834 - Posted: 19 Jul 2021, 9:15:35 UTC

Hi guys,

I'm trying to improve my resource managmente for different projects and I know how it basically works.

But I'm curious with which value the software calculates the priority of the tasks/projects.
Is it CPU-time, average points (last x weeks), total points, or maybe something else?

Thanks a lot, Robsanium
ID: 104834 · Report as offensive
Profile Dave

Send message
Joined: 28 Jun 10
Posts: 1501
United Kingdom
Message 104835 - Posted: 19 Jul 2021, 11:10:42 UTC - in response to Message 104834.  

If you don't have many projects on a machine it is much simpler.

Basically, if you add up all your projects' resource share numbers, each individual number divided by the total gives you the amount of time allocated to that project. This is a long term average however and in the short term there are lots of things that can screw it up. One is a mixture of projects that have very long tasks and those with very short tasks. An older CPU can for example with CPDN take over a month to complete a task. (my ageing netbook would take about three months with the longer current tasks!) Another is tasks with very short deadlines. In theory projects shouldn't give you tasks that won't get completed in time but like many theories it doesn't always work. BOINC will prioritise tasks that would otherwise go past their deadlines, messing up the resource share allocation in the short term.

I seem to remember there is a way to set the time period over which BOINC will even things out but never having used it I can't remember the details except that it involves manually editing one of the .XML files that BOINC produces.
ID: 104835 · Report as offensive
Robsanium

Send message
Joined: 19 Jul 21
Posts: 2
Message 104841 - Posted: 19 Jul 2021, 13:38:40 UTC - in response to Message 104835.  

Thanks a lot for your response.

CPDN is actual the reason I asked.
I've calculated the project resources with running-time as the crucial value, because WCG (for example) uses a different credit system.
But - against my calculation - boinc does a lot more from these several-day-tasks from CPDN, instead of the other projects with higher priorities/a lot less time to return.
Yeah, you are completly right ... because of the "a lot things can screw it up" I wanted to make sure, atleast my calculation isn't completly wrong :D
Soo, let's wait and see, if boinc does it the way I want it at some point ... otherwise, I'll help other projects, could be worse.

Thanks again, and have a nice start in the week.
ID: 104841 · Report as offensive
Profile Keith Myers
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 17 Nov 16
Posts: 611
United States
Message 104845 - Posted: 19 Jul 2021, 19:20:52 UTC - in response to Message 104835.  
Last modified: 19 Jul 2021, 19:35:14 UTC

Edit the <rec_half_life_days>10.000000</rec_half_life_days> field in <proxy_info> section to <rec_half_life_days>1.000000</rec_half_life_days> of the cc_config.xml file and it will converge the resource share between multiple projects faster.
REC or Recent_Estimated_Credit is one of the many mechanisms that can perturb the default BOINC resource share settings. Deadlines and amount of workdays in caches are the other primary mechanisms.

That mechanism tried to balance/equalize the awarded credit totals between projects. And because projects are free to choose to follow/not follow the standard credit_new credit award algorithm, projects that award arbitrarily high credit for tasks skews the REC algorithm in the favor of lower awarding projects.
ID: 104845 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4642
United Kingdom
Message 104846 - Posted: 19 Jul 2021, 20:50:45 UTC - in response to Message 104845.  

... field in <proxy_info> section ...
No, it's an option in it's own right, alphabetically next after 'proxy'.

Always refer new users back to the User Manual, in this case the Client configuration / Options section.
ID: 104846 · Report as offensive
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 174
United Kingdom
Message 104848 - Posted: 19 Jul 2021, 22:42:17 UTC - in response to Message 104841.  

Thanks a lot for your response.

CPDN is actual the reason I asked.
I've calculated the project resources with running-time as the crucial value, because WCG (for example) uses a different credit system.
But - against my calculation - boinc does a lot more from these several-day-tasks from CPDN, instead of the other projects with higher priorities/a lot less time to return.
Yeah, you are completly right ... because of the "a lot things can screw it up" I wanted to make sure, atleast my calculation isn't completly wrong :D
Soo, let's wait and see, if boinc does it the way I want it at some point ... otherwise, I'll help other projects, could be worse.

Thanks again, and have a nice start in the week.


As far as I can tell this is because CPDN only updates it’s credit score weekly, therefore the calculated PED is always much lower than the projects that update daily and it gets preferential treatment.
ID: 104848 · Report as offensive
Profile Keith Myers
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 17 Nov 16
Posts: 611
United States
Message 104849 - Posted: 20 Jul 2021, 2:51:25 UTC - in response to Message 104846.  

Thanks for the correction Richard.
ID: 104849 · Report as offensive

Message boards : Questions and problems : crucial value for resource management

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.