Your host looks like it can handle the load. It may take a little bit for things to settle down. A newly attached project tends to download a bit more work than it should. A newly install client also tends to download more work than it should. I have slower hosts than yours attached to almost all of the projects in my sig without problems.
As long as you can complete 1 work unit in the time required it won't matter long term. The scheduler will run einstien exclusively to get it done on time, and then run seti exclusively to catch up to your set work shares.
I resumed using this PC a few days ago (after a pause of one month) only to find out, that new wus will take 70 - 100 hours and it gave me two weeks to finish them. This will never be possible by my PC usage, I would have to let it run for several days.
Well to sum it up, we are basically Beta Testing the new app for the next full length run.
The current version of the app is setup for debugging, has little to no optimization in it, as well as some other problems.
That being said once it gets back to a more mature state and optimized again, we should see a marked improvement in performance. I wouldn't surprised if even then it takes more time to run a result than we've seen before, but since Dr. Allen and Bernd haven't said anything at this point about increasing the deadlines, my guess is they feel late model hosts will be able to complete them in time under the usage patterns people have had in the past.
Packets are too large
)
Your host looks like it can handle the load. It may take a little bit for things to settle down. A newly attached project tends to download a bit more work than it should. A newly install client also tends to download more work than it should. I have slower hosts than yours attached to almost all of the projects in my sig without problems.
BOINC WIKI
BOINCing since 2002/12/8
As long as you can complete 1
)
As long as you can complete 1 work unit in the time required it won't matter long term. The scheduler will run einstien exclusively to get it done on time, and then run seti exclusively to catch up to your set work shares.
RE: The packets are too
)
Be patient, wus need many hours. ;)
(with my Barton 3200+, i need 1 day/wu)
[
The packets are really too
)
The packets are really too large!
I resumed using this PC a few days ago (after a pause of one month) only to find out, that new wus will take 70 - 100 hours and it gave me two weeks to finish them. This will never be possible by my PC usage, I would have to let it run for several days.
Before, wus were a few hours which was OK.
Something is going on...
But what???
Thanks for enlightenment.
Luigi
Well to sum it up, we are
)
Well to sum it up, we are basically Beta Testing the new app for the next full length run.
The current version of the app is setup for debugging, has little to no optimization in it, as well as some other problems.
That being said once it gets back to a more mature state and optimized again, we should see a marked improvement in performance. I wouldn't surprised if even then it takes more time to run a result than we've seen before, but since Dr. Allen and Bernd haven't said anything at this point about increasing the deadlines, my guess is they feel late model hosts will be able to complete them in time under the usage patterns people have had in the past.
HTH,
Alinator