Well im not getting that at all. i have three computers crunching just milkway. and each of them gets ONE wu each crunch it send it report then wait about 30 sec before getting a new work unit and this has been happening since the upgrade.

That is odd. What are your connection settings?

Things have been flowing nicely since the db purge :)

I think it is more due to upgrading the Boinc server platform....Hey didn't ya'll say you were going to try the per cpu method of handing out work with the upgrade? Coming soon?

Well,

max_wus_in_progress
Maximum results in progress per CPU. Setting this to something (like 2 for instance) will limit the number of results a given host can simultaneously have registered as 'in progress'.


We have that option set to 20. So you should be getting 20 wus per cpu i believe.

That's what I'm getting, 20.

20 in total...or 20 per cpu? Because it should be 20 per cpu, i think we have it capped out at 50 total right now. Which is easily changeable.

Things have been flowing nicely since the db purge :)

I think it is more due to upgrading the Boinc server platform....Hey didn't ya'll say you were going to try the per cpu method of handing out work with the upgrade? Coming soon?

Well,

max_wus_in_progress
Maximum results in progress per CPU. Setting this to something (like 2 for instance) will limit the number of results a given host can simultaneously have registered as 'in progress'.


We have that option set to 20. So you should be getting 20 wus per cpu i believe.

Don't worry about it Dave, it we don't get it in todays stats, we'll get them in tomorrows.

But Philadelphia ..its just a bug report so Dave can fix it....if he doesn't know he can't fix can he? :=)

Hey Everyone,

I made it so this forum was useable to express anything you might have to say. The reason you see so many errors is because we're upgrading to PHP 5 which the new php files are but we're currently on PHP 4. However, there still is some base functionality while we're doing this. Sorry for the inconvience.

One tiny bug - The yellow 'unread' posts indicator isn't working any more.

Al.

That's a bug in the boinc code... same as at seti@home.
It works as long as you don't use the "back" button in your browser.

Good call, I hadn't noticed that.

Yeah, we're trying to fix the assimilator problem. It seems to be working, however it's either reprocessing already processed wus or not deleting them. Either way it's a problem so we're purging the db. After that done, you guys should be receiving work like you were. I'm also in the process of upgrading the server software, however I'm having trouble compiling because it wants to link with some non existant graphics libraries. We'll figure it out though.

Real crunchers don't need no stinkin graphics....... :)