How do you set which project gets the lion share of the work done?? How do you change the resource share and scheduling priority setting and which controls which project gets more CPU time? I only run 2 projects. Thanks in advance for helping a newbie.

---

You set the resource share in your project's preference pages.
(as opposed to on the Computing preferences page which applies to all projects)

Claggy

Thanks a bunch, found it. Got it set but the one I set to a lower resource is still getting more work units run. Didn't see anything anout the scheduling priority setting so not sure why Rosseta seems to be getting more units run than SETI.


Thanks for the help anyway, I knew it had to be right in front of me but was bugging the crap out of me.

---

Thanks a bunch, found it. Got it set but the one I set to a lower resource is still getting more work units run. Didn't see anything anout the scheduling priority setting so not sure why Rosseta seems to be getting more units run than SETI.

Boinc decides the scheduling priority, now adays it's a REC-based scheduler, as opposed to time based.

How many tasks in progress do you have from Seti? At present there is a limit of 100 CPU tasks and 100 GPU tasks in progress at Seti, if you're at the limits, then any other project will fill up your cache:

Continued server problems.

We're continuing to have issues due to a database problem early last week and a botched attempt to fix it.

The problem is that the result and host tables in the database have grown large enough, and hosts have gotten fast enough that the lookup of result in process for a host and the enumeration of new results to send don't finish before the web connection times out either on the server or the client side. This resulted in hosts being assigned large number or results to compute without the transaction that tells them about these results being completed. The host. think it received no results would then contact the server for more results, which it would again not receive.

This isn't a hardware problem. The database currently fits in memory and the processors are fast. We've just crossed a threshold where each host computes fast enough that host queues and the result table have become large enough to cause this problem. To solve it, we've put per host limits on results in process back in place. But hosts that are having this problem will probably continue to have it until the average number of results per host has fallen to a workable level. That could take weeks.

Claggy