What makes a task "High Priority"? |
![]() |
| log in |
Message boards : Number crunching : What makes a task "High Priority"?
1 · 2 · Next
| Author | Message |
|---|---|
|
Just looking at my task list, I see that two tasks were stopped in progress and two other tasks are now "Running, High Priority". Just curious what that means. And yes, I'm new... | |
| ID: 1346358 · | |
|
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. | |
| ID: 1346362 · | |
|
Thanks. I just looked at the deadline dates on the stuff sent to me, and while most is due April and into May, these two are due 3/26 and were buried down the list. | |
| ID: 1346363 · | |
|
And sometimes tasks go HP for no apparent reason whatsoever, especially if you run Einstein as well as Seti. | |
| ID: 1346372 · | |
|
I can artificially generate "high priority" by limiting the number of cores I'm using for SETI (which I do while gaming). Suddenly from the POV of the manager, it sees it'll take three times longer to process all the CPU units assigned which impacts shorties that only have a delivery date like two weeks after being assigned (instead of like six weeks for normal units) so any shorty I have waiting to be processed gets bumped up to the run NOW, while the unit that was being processed gets put on standby. | |
| ID: 1346387 · | |
|
It is also worth noting that it will depend on your BOINC version, which task will run in HP. Some versions strictly enforce EDF - earliest deadline first - while others will choose tasks further down the list - those that the simulation has decided will not make it in time if the normal FIFO (first in first out) order of running is used. | |
| ID: 1346469 · | |
Thanks. I just looked at the deadline dates on the stuff sent to me, and while most is due April and into May, these two are due 3/26 and were buried down the list. If you Click on The Little Arrow in the Heading of the Column 'Estimated Time remaining'it will Rearrand Your List. So it may not have actually been 'Buried' in The List, it may have just been the way it was displayed. ____________ GALAXY-VOYAGER | |
| ID: 1346570 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. What about when freshly *Downloaded Tasks are Added at the Top of The List above Currently Running Tasks, which are suspended upon Completion of such Download, and the New One is Started and Run as HP. And when *it finishes, another fresh downloaded task does the same thing. Hence resulting in the remaining Tasks being given less chance of Completing On Time ? ____________ GALAXY-VOYAGER | |
| ID: 1346571 · | |
Thanks. I just looked at the deadline dates on the stuff sent to me, and while most is due April and into May, these two are due 3/26 and were buried down the list. And after you've done that you might want to check this post for how to get the boinc manager to display the tasks in order of arrival again... ____________ A person who won't read has no advantage over one who can't read. (Mark Twain) | |
| ID: 1346585 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. A project that is running in HP should NOT fetch. That may be different in recent versions, where workfetch is governed by the amount of work recently done for a project, besides the cache levels. However if you throw the system out of balance (and starting fresh IS out of balance) it can take a while to settle down. ____________ A person who won't read has no advantage over one who can't read. (Mark Twain) | |
| ID: 1346590 · | |
Thanks. I just looked at the deadline dates on the stuff sent to me, and while most is due April and into May, these two are due 3/26 and were buried down the list. (I just Edited the above information I Posted earlier: I previously stated the Column Labelled 'Estimated Remaining Time'.... however, it should be 'Deadline' as I have Edited it to. Sorry if I caused any confusion by Posting the incorrect information before). ____________ GALAXY-VOYAGER | |
| ID: 1346591 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. If Normal tasks keep getting pre-empted in favour of shorter deadline tasks, then eventually those Normal tasks will get into deadline trouble, then Boinc will do those in High priority, and will likely stop asking for work from that project until that hurdle is overcome, (depends on the number of cores available, and the split of work across them) Claggy | |
| ID: 1346592 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. Okay, thanks for the information. The Computer I'm referring to is a HP Notebook G64 with Windows 7. It's Dual Processor and I presently only have my preferences set to use 1 (one) Processor at 100%. I'm not using both processors because I only have 2GB RAM and I use the machine for General Work whilst SETI is running (and CPU Usage is between 60% and 80% at the Best of times: But often runs at 70%-99%). I ONLY run SETI on this machine. There are currently about 69 tasks in The Queue (including 2 partially completed ones) It only runs One Task at any one time. What I was thinking of trying, was to select 'No New tasks' until I cleared some of the Existing ones. do you think that would this be worth Trying. I mostly have it running 24/7, except i may put it in Sleep mode for a few hours each couple of days, and once or twice a week I Shutdown for 4 to 6 hours or overnight (just to give the system a Rest). Could I possibly Reset Preferences to use both Processors without causing problems? If so, should I only run it for a Certain Number of hours per day? ____________ GALAXY-VOYAGER | |
| ID: 1346596 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. okay thanks. however, what is actually happening is when The HP has completed, it then fetches New Work. Or, if it does not Immediately fetch new work, and resorts back to one that it was previously processing, when it Uploads THAT one alone, or with any additional ones it has since completed, it then fetches new Work, which recently has been the HP Ones. It not actually Fecthing new Work whilst a HP is in Progress. ____________ GALAXY-VOYAGER | |
| ID: 1346599 · | |
Basically it means that BOINC thinks based on what you have left in your cache + how long it will take to crunch them + how much time you have until the deadline + what your "connect every x days" setting is set for, that you might not be able to report that task before the deadline, so it gets moved up to high-priority to make sure it completes before the deadline. Just don't cache so much, and don't worry about it. High priority is designed to prevent tasks over-running their deadlines - it's perfectly normal and doesn't affect your computer at all. | |
| ID: 1346601 · | |
Okay, thanks for the information. The Computer I'm referring to is a HP Notebook G64 with Windows 7. It's Dual Processor and I presently only have my preferences set to use 1 (one) Processor at 100%. I'm not using both processors because I only have 2GB RAM and I use the machine for General Work whilst SETI is running (and CPU Usage is between 60% and 80% at the Best of times: But often runs at 70%-99%). What cache settings are you running? Claggy | |
| ID: 1346603 · | |
|
As others have said, if you leave BOINC alone, it will sort itself out eventually. | |
| ID: 1346650 · | |
|
i could be wrong here (really it does happen now and then) but i think that if a task have been resent many times with no quorum then when it gets sent out as a new wu download it gets set to high priority. | |
| ID: 1347174 · | |
|
Re-sends are sent out with a normal length deadline. And so run a normal priority, unless the rules outlined in earlier posts apply. | |
| ID: 1347199 · | |
|
We may have an issue with high priority. I have every task that is running is running under high priority. Two of them are not due until 04/02 and my computer runs 24 hours a day and can handle 4 tasks at once. One for 04/02 is waiting and then until 04/08 all are under 2 hours estimated time. I don't think these should be high priority as they will all be finished by 03/22/13 which is 13 days before they are due. | |
| ID: 1348845 · | |
Message boards : Number crunching : What makes a task "High Priority"?
| Copyright © 2013 University of California |