I have CPDN & SETI set up to run, with the ratio of CPDN to SETI being about 9:1. I'd expect to see the processes running around 9 hours CPDN to 1 hour SETI, but I'm actually getting a ratio of about 50:50. Every hour the despatcher swaps process.

Is this just because the despatcher doesn't work, or is the despatcher calculating the share of resources based on a large sample?

CPDN started first, and has used much more than 90% in the period since I installed BOINC 4.05. Could the despatcher simply be allowing SETI to catch up?

Suggestions?



Giskard - the first telepathic robot.

CPU Scheduling in Ver 4.05
Client scheduling policies





M7 Seti@h Berkeley's Staff Friends Club ©

CPU scheduling has got you. Doing CPDN and Seti at a 9:1 ratio will not allow the Seti WU's to complete before their due date. Somethings got to give. I believe that they need to rethink this somehow considering rather extreme differences in the due dates at CPDN and SAH. If your ratio was 1:9, you'd have no problem.

---

Account frozen...

> CPU scheduling has got you. Doing CPDN and Seti at a 9:1 ratio will not allow
> the Seti WU's to complete before their due date. Somethings got to give. I
> believe that they need to rethink this somehow considering rather extreme
> differences in the due dates at CPDN and SAH. If your ratio was 1:9, you'd
> have no problem.

Because Boinc/Seti CANT correctly calculate the time to completion of one unit(deviations +/- 100%) it should not calculate the time needed to process all units before report deadline ;-)

>>Doing CPDN and Seti at a 9:1 ratio will not allow the Seti WU's to complete before their due date

Not so. Alone, a SETI unit runs to completion in about 4 hours. A 9:1 ratio should complete a SETI unit in about 40 hours (along with 36 hours of CPDN) - well within the SETI unit deadline. Even if a SETI unit were to take 10 hours, a 9:1 ratio should allow it to complete in a little over four days. I have kept the cahce size down - maximum of two SETI units at a time, and then only when the first is well through its computation.

>>CPU Scheduling in Ver 4.05
>>Client scheduling policies

Pascal, I looked at these pages. The algorithm described appears to work for my scenario. The implementation appears to fail.


Giskard - the first telepathic robot.

I was noticing similar behavior: 50/50. However, after a reboot, I'm seeing more what I expected with the resource sharing. Have you restarted since changing/setting your resource settings?

>>Have you restarted since changing/setting your resource settings?

Good Point - the affected machine runs 24/7. I haven't even restarted BOINC since I installed it. I'll restart and see what happens...

Watch this space!


Giskard - the first telepathic robot.

CPU scheduling has got you. Doing CPDN and Seti at a 9:1 ratio will not allow the Seti WU's to complete before their due date. Somethings got to give. I believe that they need to rethink this somehow considering rather extreme differences in the due dates at CPDN and SAH. If your ratio was 1:9, you'd have no problem.
==========

Thats the way I set mine up Dogbytes, 90-10 90 for Seti & 10 for CPDN. So far it seems to work because every now and then it will run 1 hour of CPDN and then revert back to running Seti for I don't know how long but for quite awhile anyway....Seems to be working good that way since Seti is my preferred project anyway... :)

I tried rebooting. It didn't seem to have any effect.

> I have CPDN & SETI set up to run, with the ratio of CPDN to SETI being
> about 9:1. I'd expect to see the processes running around 9 hours CPDN to 1
> hour SETI, but I'm actually getting a ratio of about 50:50. Every hour the
> despatcher swaps process.
>
> Is this just because the despatcher doesn't work, or is the despatcher
> calculating the share of resources based on a large sample?
>
> CPDN started first, and has used much more than 90% in the period since I
> installed BOINC 4.05. Could the despatcher simply be allowing SETI to catch
> up?
>
> Suggestions?

Did you reload your preferences? With the Linux CLI BOINC 4.05 client:

(Where "boinc" represents the actual name of the executable)

./boinc -update_prefs http://setiathome.berkeley.edu

Will update your BOINC preferences.

The solution is simple...


The percentage you donate to a project should be the percentage of time YOUR CPU works on each.


If you pick 1% for project it should work on it 1% of the time.


The way it is now setting a project for 99% and another for 1% means it's switching at about a 50/50 ration....which isn't in proportion to what is set.


and obviously filling up the cache when both projects are up and running with alot of the 1% WU's is equally silly...it should download them 1 at a time and complete it before it downloads another. In the chance the 99% project is down it can go to town and fill itself with the 1% project wu's...but you would expect it to complete every WU save for 1 and then go back to crunching on the 99% project when it's back up.


Most users don't really want resources to be figured over time...they want resource alocations to be immediate. If one project goes down for 45 days...most wouldn't want BOINC to try and catch back up with the other projects. They would simply take it as they may and want the cpu to go back to spending the % of resources they assigned to each project.

I think the big problem is the Preferences either don't work or gets reset every time the Server lets a Fart.

I just set up a seperate Work Preference for 1 Computer a little while ago so it wouldn't Download so many Seti WU's because I have 2 CPDN WU's sitting there waiting to be done.

So I thought I would set it up so it would run out most of the Seti WU's I had on that Copmuter & then I was going to set it up to be a 50/50 Computer between Seti & CPDN.

I hit Update and everything seemed to get Updated so I started BOINC back up and what does it do, download more Freaking Seti WU's even though I set the Preferences for that PC to almost nothing...D'oh...So now I have even more Seti WU's to run off that Computer before I can set it up to run 50/50 between the 2 Projects...Sigh, now where the Hell is that Detach Tab again... :/

JOIN TEAM
[/url]