[openbeos] Re: Off-Topic: Con Kolivas quits Linux. He should know Haiku
- From: Stephan Assmus <superstippi@xxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 10 Aug 2007 12:14:29 +0200
Hi André,
> > as Con says in his interview, and then give the user the possibility to
> > choose which application should get more attention by the CPU by simply
> > right clicking on the top bar
> > of the window application, instead of having to open a terminal and use
> > nice?
>
> This is not intuitive, this is micromanagement of computational
> resources. More about this on the eventual blog post.
I don't mean to be pushy... but I'd *love* to see some code! :-)
I probably won't understand half of your eventual blog post, but I
understand that our current scheduler has some problems that need fixing...
;-)
For example, a high priority thread can make the system *appear* to lock up
completely. In fact, I have not had a true lockup of the app_server in
months. Yet it seems like that can happen, while it is only some amok
running menu or the like. In fact, with our priority based threading, which
is founded on the assumption that interactive threads get a high priority
and non-interactive, number crunching threads get a low priority, I'd love
if the scheduler would automatically unreal any high priority threads that
suddenly consume a lot of CPU. Since the assumption is that this is not
supposed to happen on our desktop tailored system.
Best regards,
-Stephan
Other related posts:
