Lowest Resource Share Setting
16 Jul 2007 11:58:24 UTC
Topic 192969
(moderation:
I would like to know what the LOWEST Resource Setting can be and still be able to get work from E@H.
This would help folks that run more than one project so that we can know how many can be attached and still get WU's.
Lowest Resource Share Setting
)
AFAIK, it can be as low as you want. Sending work is not strictly a function of the resource share.
However, as you go lower in share, the limiting factor is how much LTD the project with the low share has developed. Worst case would be when it gets above the final run time estimate (like you see in scheduler logs here). Then BOINC should DL a result for the low share project, but then it would have to run the result primarily in EDF to make the deadline, after which the project would go 'idle' until the cycle repeats.
Depending on the exact circumstances this could be weeks or months.
HTH,
Alinator
RE: I would like to know
)
While you might get WUs in any case, you will not be able to crunch the most demanding workunits within the current deadline of 2 weeks unless your RAC is about (say) 50. How low you set your resource share and still get 50 credits per day depends on the performance of your PC, how long you keep BOINC active each day and the load from other applications on the computer.
CU
BRM
You can have as many projects
)
You can have as many projects as you want per host. The client will rotate which project(s) have work on your host. If you look at my sig any project with more than 60 RAC is probably attached to a 500mhz host. That host usually has work from 3 or 4 projects at a time of the 10 or so attached.
If you want work from all projects attached you will have to discover the limits by trial and error. We can not answer your question since different hosts and combinations of projects will produce different results.
BOINC WIKI
BOINCing since 2002/12/8
Agreed, RAC is irrelevent
)
Agreed, RAC is irrelevent when it comes to whether your host will get work or not. The determining factor is if it probable for your host to complete the work within the deadline if it wasn't running anything else.
If that is true, the resource share and LTD will determine how much and how frequently your host will run work for a project with a very low resource share.
As I said, depending on the speed of the host that might not be very much or very often. ;-)
Alinator