yoyo wrote: Wed Apr 15, 2026 7:14 am
As also in yoyo@home, not all work is already a BOINC workunit in the DB. This keeps DB small and fast.
You can also see that yafu (and yoyo@home) runs never out of work. So your indicator of declining number of available tasks seems to be wrong.
Additional in yafu each result leads automatic to a new workunit. So yafu just needs as much workunits as needed to cycle through the volunteer computer and an additional buffer.
In kiskas grafan you can see, that round about 500 workunits are processed (each of them leads to a new workunit) and that 3 times more tasks, round about 1500, are available to sent out.
You can also see, when tasks in progress are increasing, also available tasks are increasing.
tldr;
What kiskas grafana shows of available tasks and what is base on your decission, is not the reality. It is just a small part of available tasks.
yoyo
Hi
Thanks for your input.
Firstly, I recognise that every project has their own processes by which they make work units available. And generally, speaking this is not something that is shared in the public domain or to me in person.
So, that puts me in a tricky place as I cannot "guess" if a project can withstand the high demands placed upon it by a Sprint.
And I use the grafana website as an indicator of which projects have available tasks, so I can then de-select all the ones that are offline or have few tasks available - and that website saves me a lot of work as otherwise, I'd have to visit every project website, every day to check the task availability...and frankly, I do not have the time to do this, as in the real world, I have a business to run and I have a personal life as well.
Of course the stats shown on grafana might be slightly wrong...but I do not really have any other choice, as I can select on their website, the length of time to show the stats...so I can look at 7 days worth of stats to see a trend.
Also: we both know that if FB Teams and Members cannot get enough tasks, then a) I get blamed and b) the project gets blamed. And I really want to avoid this, which is why I try to make contact with project admins a week before a Sprint so that they are prepared.
Ultimately, it is up to project admins to generate enough tasks for their day to day operations and if they can ramp up the number of "ready to send" tasks, just for a Sprint, then that's even better.
If you want to send me a PM with a proposal for a specific date when one of your projects would be chosen, then I'm happy to give it a test and we can then see how it goes.
regards
Tim