Message boards : Number crunching : Tells us your thoughts on granting credit for large protein, long-running tasks
Previous · 1 . . . 6 · 7 · 8 · 9
Author | Message |
---|---|
mikey Send message Joined: 5 Jan 06 Posts: 1895 Credit: 9,161,627 RAC: 4,094 |
Intel's next generation of CPUs actually looks like it might be not just competitive against AMDs current offerings, but possibly even better. Some early tests for you for the 'Intel Core i5-12600K CPU Up To 50% Faster Than Ryzen 5 5600X' https://wccftech.com/intel-core-i5-12600k-cpu-faster-than-ryzen-5-5600x-blows-away-rocket-lake-core-i9-11900k-leaked-benchmarks/ |
LumenDan Send message Joined: 26 Apr 07 Posts: 3 Credit: 5,554,576 RAC: 862 |
Incentives are nice but I think it's important to make up for lost CPU time in the case where the BOINC scheduler hits a memory limit and reduces the number of active work units on a multi thread CPU hence under-utilising the hardware. It would pay to check statistics of active computers and typical hardware utilization options for contributors to get a baseline system for project contributors but lets take a system with 8 "cores" as an example of a recent generation mid performance system: A CPU that can process 8 work-units in parallel it would require 8GB of available RAM to allow full utilization of the CPU @1GB of RAM each. The same configuration could only support two concurrent work units @4GB of RAM each resulting in a CPU utilization as low as 25%. A system with 2GB of RAM per processing core would still only result in 50% CPU utilisation. If the project Admins can formulate an average "available GB RAM per processing core" ratio for contributors it could be used to calculate the lost %CPU utilization and a reward could be formulated to compensate for lost processing capability. Alternatively, the Admins and/or community could nominate a ratio of RAM per processing core that would best suit the majority of contributors and the reward could be calculated using that reference system. eg: If we think 2GB per processing core is reasonable then a 50% credit bonus would be fair to make up for lost computation time. Of course BOINC scheduling is never that straight forward unless you consider a user that is only crunching for Rosetta and all of the resources are dedicated simultaneously to large memory work units, but, unless we expect contributors to edit config files the worst case should be considered. Personally I would rather see contributor hardware better utilised than receive bonus credits for poor performance, that may require stricter memory limits on the high RAM work units to reduce the likelihood of reaching memory limits in the first place. |
miyamotomusasi Send message Joined: 29 Sep 22 Posts: 10 Credit: 0 RAC: 0 |
Your posts are always a pleasure for me. I will continue to read your articles. You always appreciate good posts. :) 메이저토토 |
Stevie G Send message Joined: 15 Dec 18 Posts: 107 Credit: 837,101 RAC: 1,615 |
I think you need to allow more than three days for completion. I can do those, but at the expense of my other projects. S. Gaber |
Speedy Send message Joined: 25 Sep 05 Posts: 163 Credit: 808,098 RAC: 0 |
Before you can grant any credit you need to have tasks available to distribute. Credit is always good you don't want to march or you will only get people that are hunting for credits. Those are my thoughts Have a crunching good day!! |
Message boards :
Number crunching :
Tells us your thoughts on granting credit for large protein, long-running tasks
©2024 University of Washington
https://www.bakerlab.org