My projects' Resource shares are set thusly: Rosetta at 90%, World Community Grid at 9% and Einstein at 1%. Therefore when Rosetta isn't running (often in the last year), my computer should be running 90% WCG tasks and 10% Einstein tasks, right? However, I haven't had any Einstein tasks in days and days. Even when I "Update" Einstein, I don't get any tasks. Does anyone have an explanation for this? Thanks. https://www.boincstats.com/signature/-1/user/38349/sig.png
Copyright © 2024 Einstein@Home. All rights reserved.
googloo wrote: My projects'
)
Your request seems to be very vague. It would help to help you with a little more information, like what tasks are you trying to run in Einstein, what your preferences are and not just the Resource shares, etc.
Proud member of the Old Farts Association
googloo wrote: My projects'
)
First it's about RAC not tasks and second I don't think it works that way, I think Boinc keeps trying to get Rosetta tasks and Einstein stays at it's 1% of the total RAC put out by your pc. That means that if WCG gives you 1000 credits for a task and Einstein does the same then it will be awhile before Einstein gets another task.
The OP has 2 computers
)
The OP has 2 computers currently making contact with the project. Each one made a request for CPU work as shown in the most recent scheduler request link on his computers page. Since no work was supplied, a possible reason may be that he doesn't have a current CPU search enabled in his preferences.
@Googloo - What CPU searches (ones with available work) have you ticked in your prefs?
Cheers,
Gary.
Thank you. I've adjusted my
)
Thank you. I adjusted my preferences, got new tasks.
mikey wrote: googloo
)
I didn't know this either. The percentages that we select are based on RAC?
REC or Recent Estimated
)
REC or Recent Estimated Credit is a algorithm BOINC uses to balance credit among your projects.
So running one project exclusively and then adding another project or switching to another project makes that new project owe a credit debt that causes it to run exclusively trying to catch up to the RAC of the original project.
So your original project will not get any work while the other project is playing catchup.
You can shorten this effect by changing the time limit the algorithm is working under from the default ten days to just one day in the variable in the cc_config.xml file.
Change <rec_half_life_days>10.000000</rec_half_life_days>
to <rec_half_life_days>1.000000</rec_half_life_days>
in the <Options> section
This works independently of your Resource Share percentages on projects. But changing your Resource Share suddenly exaggerates the effect.