| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
WilhelmGGW
Advanced Cruncher Joined: Nov 12, 2005 Post Count: 52 Status: Offline Project Badges:
|
I have BOINC/WCG installed on several computers with PC, Mac, and Ubuntu OSs. It strikes me how each OS -- when compared to the others -- is better (faster) at some projects and worse (slower) at others. That is, that each projects runs better or worse on one OS compared to on others.
Does WCG take this into account, to distribute to each computer a preponderance of selected projects that run best on its OS? That is, if I have 5 projects selected for all to run on, that, say, my Ubuntu machines mostly get work units of the project(s) it handles better that the other OSs, etc. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This is on the wanted wish list as an ''opt-in'' so hosts would work at what they're most performant on, but unsure whether this finds many adopters... WCG bossing hosts around. A ''best at'' but only on your selection, probably will entail a repeated testing to discover which of the selected combo is, since a device's make-up will be coming in infinite variations and user loads... idle / left alone may see different throughput than when the device is doing render service or whatever. Linux system are poor at CEP2 when also "used", at least that's what I'm observing.
----------------------------------------What is coming in the future when more 64 bit compiles are available, is a test if 32 bit or 64 bits process faster on a host [10 or 20 of each, to discover which is on average faster. Of course, that would only work for those devices on dual capability systems. --//-- [Edit 2 times, last edit by Former Member at May 24, 2012 9:37:04 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
To add, such assignments would be subject to availability at time of work-call i.e. a host may not always get the most optimized work for that device.
--//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello WilhelmGGW,
I will add an observation. WCG runs a number of projects on BOINC. BOINC was initially designed to run one project per website, allowing BOINC users to choose individual projects and percentage of cpu time to allocate. BOINC continues to evolve but I expect that WCG specific code will be very short on flourishes for a while. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello WilhelmGGW
Reference: WilhelmGGW [May 24, 2012 9:18:40 PM] post If you are interested mainly at machine performance or efficiency ---------------------------------------------------------------------------------- I think that it is technically possible for the WCG-servers to provide the infrastructure-support to do the clientLoad-to-clientDevice matching to come up with an optimized project WU distribution. At this point, that sounds costly though. If you won't mind the extra effort entailed, for now, you can have all the data you need to make decisions as to what among your computers crunches what WCG project for a criteria (most-efficient, most performance, etc). As soon as you have the data, you can manipulate your project-settings, profiles, etc to match the project offerings from WCG. This calls for a lot of work from your end -- and much of that is because there is no automated way to do it, for now, at the client-side. If a project's "value" is more important ------------------------------------------------- Some people don't care much about the machine's performance or efficiency. As long as it's not too bad, these people are fine with a project that they see as having value, significance, or meaning. Because these people also contribute to the grid effort, part of the incentive to focus on purely machine performance or efficiency is thereby diluted. Combine this with the server-side cost in supporting clientLoad-to-clientDevice matching, and I'm afraid that you will have to do with the manual method... for now. ; |
||
|
|
|