Another of my boxes is today on MW.

Task list downloaded have a report deadline of today's date!

Great stuff - not a hope in hell to complete any task.

My wing will soon become very upset flying with me.

---

Another of my boxes is today on MW.

Task list downloaded have a report deadline of today's date!

Great stuff - not a hope in hell to complete any task.

My wing will soon become very upset flying with me.

Deadlines are 3 days. Today is the 15th. Deadline on your remaining unaborted task is the 18th. Looks quite normal.

Sorry

So one of my boxes must be on an incorrect date/time.

I will check it out.

Thanks

Well 3 days may be normal, but it is not enough time for a 32 hour unit on a machine running 8 other Boinc projects. Why should Milkyway get High Priority on each and every unit sent down while my others can't run at all due to the High Priority.

---

Well 3 days may be normal, but it is not enough time for a 32 hour unit on a machine running 8 other Boinc projects. Why should Milkyway get High Priority on each and every unit sent down while my others can't run at all due to the High Priority.

Why you are trying to do too much with not enough? :)
I have Q9550 and im running only 3 CPU projects same time.

I'm not running Boinc for the Prestige, High Scores, or any other reason other than I want to help as much as I can, and that includes running as many projects that is possible with my 2 cpu's. Therefore Milky Way is not fair to my other projects - so it will be stopped until further changes are applied, if at all. None of my other projects take my machine hostage and they all run and get their fair share.

---

I'm not running Boinc for the Prestige, High Scores, or any other reason other than I want to help as much as I can, and that includes running as many projects that is possible with my 2 cpu's. Therefore Milky Way is not fair to my other projects - so it will be stopped until further changes are applied, if at all. None of my other projects take my machine hostage and they all run and get their fair share.

While your comments are correct in the short term, over a the long term things balance out. Boinc has a debt system which keeps track of how much crunching it has done for each project you're connected to. You will find that after a while you won't get MW WUs for a while as the debt system tries to let the other projects catch up.

Rod

I'm not running Boinc for the Prestige, High Scores, or any other reason other than I want to help as much as I can, and that includes running as many projects that is possible with my 2 cpu's. Therefore Milky Way is not fair to my other projects - so it will be stopped until further changes are applied, if at all. None of my other projects take my machine hostage and they all run and get their fair share.

While your comments are correct in the short term, over a the long term things balance out. Boinc has a debt system which keeps track of how much crunching it has done for each project you're connected to. You will find that after a while you won't get MW WUs for a while as the debt system tries to let the other projects catch up.

Rod

Yep...what Rod said.

I have the same issue with Malaria Control.Net and have to keep the amount of work cached to be less than 1 day so that BOINC doesn't put Malaria work straight into High Priority mode.

I recommend you decrease your preference settings to be less than 1 day. It may help.

My G4 Macs will be hard-pressed just to make the deadlines. I don't begrudge the high priority the MW app needs to have a hope of finishing on time, because I know the LTD accounting will ‘keep it fair’ WRT my resource shares, but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

---

My G4 Macs will be hard-pressed just to make the deadlines. I don't begrudge the high priority the MW app needs to have a hope of finishing on time, because I know the LTD accounting will ‘keep it fair’ WRT my resource shares, but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

Such is life and the progress of technology.

But, this is where a separate GPU and CPU project would be good.

but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

I've already dropped my 400MHz host from MW because it can't finish a WU in time. Assuming that the benefits of leaving the deadline at 3 days outweighs the loss of some crunchers, I don't have a problem with that. But the project will have to consider how many hosts they will lose, when deciding to leave the deadline at 3 days, or to increase it.

but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

I've already dropped my 400MHz host from MW because it can't finish a WU in time. Assuming that the benefits of leaving the deadline at 3 days outweighs the loss of some crunchers, I don't have a problem with that. But the project will have to consider how many hosts they will lose, when deciding to leave the deadline at 3 days, or to increase it.

Project has considered that and decided 3 days because they need wu's back as soon as possible to generate new wu's.
If they make deadline longer that would slow down the project.

but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

I've already dropped my 400MHz host from MW because it can't finish a WU in time. Assuming that the benefits of leaving the deadline at 3 days outweighs the loss of some crunchers, I don't have a problem with that. But the project will have to consider how many hosts they will lose, when deciding to leave the deadline at 3 days, or to increase it.

Project has considered that and decided 3 days because they need wu's back as soon as possible to generate new wu's.
If they make deadline longer that would slow down the project.

And when a GPU can do the same wu in minutes, I don't think any project would care if a few very slow hosts that take days were dropped. It is but a fact of life.

But the project will have to consider how many hosts they will lose, when deciding to leave the deadline at 3 days, or to increase it.

AIUI, and as others have implied, the deadlines are 'non-negotiable' because the computations are iterative: the results from one batch of tasks provide the inputs for succeeding batches. This cycle is already as slow as the project scientist(s) will tolerate, so the only 'free parameter' is the size of WU.

but it looks like the older systems will need more than 72 hours of CPU-time … in which case they’ll have to drop out.

I've already dropped my 400MHz host from MW because it can't finish a WU in time. Assuming that the benefits of leaving the deadline at 3 days outweighs the loss of some crunchers, I don't have a problem with that. But the project will have to consider how many hosts they will lose, when deciding to leave the deadline at 3 days, or to increase it.

Project has considered that and decided 3 days because they need wu's back as soon as possible to generate new wu's.
If they make deadline longer that would slow down the project.

And when a GPU can do the same wu in minutes, I don't think any project would care if a few very slow hosts that take days were dropped. It is but a fact of life.

If the project only cares about GPU and not about my lowliest cruncher then Ill vote with my feet NNT for all 4 boxes and then Ill be gone

---

And me

---

@ ashj and James Nelson
if you look through the forums here you will find links to optimized applications that will give you quite a bit more speed, maybe enough to let you finish a WU in time? Worth a try? The instructions are included in the readme that comes with the download, what have you got to loose? I run CPU only here too, my pentium D does a WU in aproximately 4.5 hrs,using the optimized application. So maybe your machine/s would be fast enough with the use of the optimized applications.
;-p

---

Hi Bruce,

My personal view is that I will lose my headache monitoring MW tasks. On the up side I will regain time that other projects do not require of me while crunchings on this old box.

I will therfore move on.

I sincerely hope the Project goes outstandingly well and produces great results for the boffins to analyse.

With regards

ashj

Some people just don't want to help themselves.

An optimised application is the only way forward with this project. CPU or GPU. If you are not running an optimised app you really are "cutting your nose off to spite your face".

Some people just don't want to help themselves.

An optimised application is the only way forward with this project. CPU or GPU. If you are not running an optimised app you really are "cutting your nose off to spite your face".

if you took the time to look you would see that I do run optimized they just keep upping the size till my slowest box cant return one in time.

---