A 0 resource share on a project will never request work from that project UNLESS your other projects run out of work. And then it will request exactly one task and keep doing so on a 1 for 1 basis until your other projects deliver work again. Then your 0 resource share project will go dormant again.
This is exactly what I want.
Otherwise Einstein is requesting work, the buffer is full and milkyways does only get some WUs.
Milkyway does not get continuously work units - mostly it waits until all WUs that were sent to me are computed and sent back. Then it will send new work. But Einstein is continuously getting new work - so the buffer is always full with Einstein. The 10000/1 does not work.
Your problem with Milkyway is a flaw in the scheduler logic that they can't fix. You are unable to request new work and report work in the same scheduler connection. And since MW tasks process very fast on modern gpus you are constantly reporting work every 91 second scheduler connection. So you are forced to crunch through you entire cache and never receive any replacement work until the cache is emptied. Then you have to endure a project 10 minute idle backoff till you can request new work to replace your cache. Rinse and repeat.
But that routine at MW throws a monkey wrench into using 0 resource shares at other projects as you have found out.
There are some workarounds to fix the MW problem but it involves running a custom client to get around the problem.
Did you ever look at the startup of your Event Log to see where your global preferences are loading from?
Its printed in the Event Log where the host is getting its preferences from which project or that Local Preferences are being applied to the host.
Remember the very last project you changed your preferences at are what is globally applied to ALL your projects.
Sounds like that may have been the case with Einstein. Removing and adding the project back would have gone back with the default preferences until the host made a scheduler connection.
I've never understood the benefit of using an Account Manager. It doesn't take that much effort to visit your attached projects and set your preferences for that specific project locally. All you have to do is visit the home page and login.
I read so many post of this and that the BoincStats AM is not doing what I want or whatever.
MagicEye wrote: Keith Myers
)
Your problem with Milkyway is a flaw in the scheduler logic that they can't fix. You are unable to request new work and report work in the same scheduler connection. And since MW tasks process very fast on modern gpus you are constantly reporting work every 91 second scheduler connection. So you are forced to crunch through you entire cache and never receive any replacement work until the cache is emptied. Then you have to endure a project 10 minute idle backoff till you can request new work to replace your cache. Rinse and repeat.
But that routine at MW throws a monkey wrench into using 0 resource shares at other projects as you have found out.
There are some workarounds to fix the MW problem but it involves running a custom client to get around the problem.
I have no problem with
)
I have no problem with Milkyway.
I have a problem with Einstein - or the Boinc Manager ignoring the settings from Einstein.
Milkyway works fine there are just some minutes idle time between the batches that I want to fill.
Next step will be to remove Einstein. Maybe this helps.
MagicEye schrieb: Next step
)
Yes, project removed and added again - problem solved.
Did you ever look at the
)
Did you ever look at the startup of your Event Log to see where your global preferences are loading from?
Its printed in the Event Log where the host is getting its preferences from which project or that Local Preferences are being applied to the host.
Remember the very last project you changed your preferences at are what is globally applied to ALL your projects.
Sounds like that may have been the case with Einstein. Removing and adding the project back would have gone back with the default preferences until the host made a scheduler connection.
That was a good question. I
)
That was a good question. I think I have found the victim.
Boincstats BAM! is also setting a ressource value (1) and unfortunately the BAM! setting is overriding all other settings.
I've never understood the
)
I've never understood the benefit of using an Account Manager. It doesn't take that much effort to visit your attached projects and set your preferences for that specific project locally. All you have to do is visit the home page and login.
I read so many post of this and that the BoincStats AM is not doing what I want or whatever.
I used it for attaching
)
I used it for attaching computers to a project or to start/stop work where I don't have physical access.
In the last years more and more teamviewer took over this job for me.
Hello Keith, > There are
)
Hello Keith,
> There are some workarounds to fix the MW problem but it involves
> running a custom client to get around the problem.
Can you share any details on this custom client you mention?
Thanks-
BGU
Joseph Stateson released a
)
Joseph Stateson released a special Milkyway client he developed to get around the irregularities of the MW project.
https://github.com/JStateson/MilkywayNewWork