High Priority = Wrong Priority

Message boards : Questions and problems : High Priority = Wrong Priority
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
cw64

Send message
Joined: 27 Aug 10
Posts: 16
United Kingdom
Message 37218 - Posted: 19 Mar 2011, 16:12:28 UTC - in response to Message 37137.  

Kind of a moot discussion since 6.12 has many scheduler changes, also to address the inordinate running of HP, and stop work fetch where needed. Maybe give 6.12.18 a trial and enroll in the alpha mail list to follow the discussion, though I feel it wont stand for long and the next alpha version will be compiled.

--//--



Still happening with 6.12.18

A secondary problem is that I have to run without leaving suspended apps in memory. Otherwise the constant task switching will cause me to run out of memory (no virtual mem). If you are not going to fix this problem please give the option to disable the High priority system so it runs only FIFO.
ID: 37218 · Report as offensive
SekeRob2

Send message
Joined: 6 Jul 10
Posts: 585
Italy
Message 37222 - Posted: 19 Mar 2011, 23:49:52 UTC - in response to Message 37218.  

Don't know what the best strategy is to avoid any HP, but it's hard to see how many could build up if the cache is very short combined with a long switch time so tasks complete in 1 run, most of the time which would then work kind of very close to FIFO.

As for running out of memory with LAIM on, I was told, then tested and could confirm that if that happens, BOINC will dump preempted tasks from memory if it starts to run short.

More manual switches which runs contrary to a design goal of "set and forget".
If you are not going to fix this problem please give the option to disable the High priority system so it runs only FIFO.

I'm no 'you' that can fix things. I participate on the alpha mailing list as a volunteer and occasionally insert an interruption of regular service. Some were actually taken on board and led to a fix or implementation to make crunching live better. You could do too.
ID: 37222 · Report as offensive
Max Garth

Send message
Joined: 27 Nov 09
Posts: 27
Australia
Message 37227 - Posted: 20 Mar 2011, 10:47:33 UTC

My problem is keeping 4 cores working and I think I'm heading for 8 in the next
few months. That will create a problem.
Cheersc MaxG.
ID: 37227 · Report as offensive
cw64

Send message
Joined: 27 Aug 10
Posts: 16
United Kingdom
Message 37237 - Posted: 20 Mar 2011, 19:29:20 UTC - in response to Message 37222.  
Last modified: 20 Mar 2011, 19:33:24 UTC

Don't know what the best strategy is to avoid any HP, but it's hard to see how many could build up if the cache is very short combined with a long switch time so tasks complete in 1 run, most of the time which would then work kind of very close to FIFO.

As for running out of memory with LAIM on, I was told, then tested and could confirm that if that happens, BOINC will dump preempted tasks from memory if it starts to run short.

More manual switches which runs contrary to a design goal of "set and forget".
If you are not going to fix this problem please give the option to disable the High priority system so it runs only FIFO.

I'm no 'you' that can fix things. I participate on the alpha mailing list as a volunteer and occasionally insert an interruption of regular service. Some were actually taken on board and led to a fix or implementation to make crunching live better. You could do too.


"You" wasn't aimed at anyone specific.

This is the Questions and problems forum?
This is a good place to get problems resloved?

P.S. Dumping tasks causes them to error, which is the problem.
ID: 37237 · Report as offensive
Previous · 1 · 2

Message boards : Questions and problems : High Priority = Wrong Priority

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.