Does anyone know why I have tasks that keep running high priority when they still have 10 day to the deadline, yet, with only less than a day to complete?
Boinc probably thinks that you won't finish them in time.
Are you running other projects?
About how often are your computer on and Boinc allowed to run?
If you look at your computers details here on the website what are the values for:
% of time BOINC client is running?
While BOINC running, % of time host has an Internet connection?
While BOINC running, % of time work is allowed?
The box is on 24/7 and has 100% internet access. Boinc is allowed to run all the time the box is up. (we have the occasional power cut and problems with the Broadband when the tasks just wait completed until the Broadband is restored.)
The jobs I am currently crunching are very short. Less than 3.5 hours with a due deadline of 10 days plus.
Three out of the four tasks crunch normally. Only one shows "running at high priority". This has only started recently.
The jobs I am currently crunching are very short. Less than 3.5 hours with a due deadline of 10 days plus.
Three out of the four tasks crunch normally. Only one shows "running at high priority". This has only started recently.
The "high priority" tag generally means that BOINC on your host has concluded that without help the task in question might miss deadline. Since BOINC does not make the task actually run faster, this just means a change in processing sequence of tasks in your queue. The fact the task itself is short and the deadline far away does not signify--it is the estimated time to complete the work which would otherwise run first that matters.
If you would like not to see this, you may wish to consider setting lower settings for the location (venue) used for your hosts in the computing preferences section of your account web page. It is the sum of the "BOINC will try to maintain at least this much work" setting and the "Maintain enough work for an additional" that matters.
One thing that can upset a previously stable system in this regard is a transition to a new type of work units, or a mix of work units. While BOINC can be hoped eventually to get it right (assuming your system itself is stable), it often gets temporary estimation errors in such cases, sometimes large.
Running high Priority query
)
Boinc probably thinks that you won't finish them in time.
Are you running other projects?
About how often are your computer on and Boinc allowed to run?
If you look at your computers details here on the website what are the values for:
% of time BOINC client is running?
While BOINC running, % of time host has an Internet connection?
While BOINC running, % of time work is allowed?
What are your cache
)
What are your cache settings?
Claggy
I am only crunching
)
I am only crunching E@H.
The box is on 24/7 and has 100% internet access. Boinc is allowed to run all the time the box is up. (we have the occasional power cut and problems with the Broadband when the tasks just wait completed until the Broadband is restored.)
The jobs I am currently crunching are very short. Less than 3.5 hours with a due deadline of 10 days plus.
Three out of the four tasks crunch normally. Only one shows "running at high priority". This has only started recently.
The box is hardly ever used for anything else.
Regards to all crunchers.
RE: The jobs I am currently
)
The "high priority" tag generally means that BOINC on your host has concluded that without help the task in question might miss deadline. Since BOINC does not make the task actually run faster, this just means a change in processing sequence of tasks in your queue. The fact the task itself is short and the deadline far away does not signify--it is the estimated time to complete the work which would otherwise run first that matters.
If you would like not to see this, you may wish to consider setting lower settings for the location (venue) used for your hosts in the computing preferences section of your account web page. It is the sum of the "BOINC will try to maintain at least this much work" setting and the "Maintain enough work for an additional" that matters.
One thing that can upset a previously stable system in this regard is a transition to a new type of work units, or a mix of work units. While BOINC can be hoped eventually to get it right (assuming your system itself is stable), it often gets temporary estimation errors in such cases, sometimes large.
Thank you all for all your
)
Thank you all for all your assistances.
I will leave everything as is and leave the box to sort it out.
I, at first, thought the box was on the blink and would need a replacement.
Thankfully no.
Regards to all crunchers