home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!usc!not-for-mail
- From: merlin@neuro.usc.edu (merlin)
- Newsgroups: comp.os.ms-windows.advocacy
- Subject: Re: Notice! OS2 will Execute Win3 programs Without having to have Win
- Date: 3 Jan 1993 17:11:08 -0800
- Organization: University of Southern California, Los Angeles, CA
- Lines: 17
- Message-ID: <1i82rcINNl68@neuro.usc.edu>
- References: <1993Jan3.215505.21543@cs.uoregon.edu> <1i7p0mINNkkc@neuro.usc.edu> <1993Jan4.005023.26661@cs.uoregon.edu>
- NNTP-Posting-Host: neuro.usc.edu
-
- >Thus, if a process needs a lot of processing time to handle an event, it can
- >take it; but if a process doesn't need to do anything (a "background" process
- >wouldn't have to do much) in response it a message, it can (and usually does)
- >yield control almost IMMEDIATELY to the next process that has high-priority
- >messages pending. In a sense, this is a form of self-imposed priority-based
- >scheduling.
-
- YES! BUT! That works for well behaved well written Windows applications.
- However, when you try doing background compiles of large application source
- codes (200,000+ lines of C) then the lack of dynamic priority scheduling
- becomes particularly evident. I am informed this is true largely of apps
- running in a DOS box and not of regular Windows apps. However, working as
- a developer of cross system applications (OS/2 2.1, SCO UNIX, 386BSD-0.1,
- and maybe DOS/Win32s), the lack of preemptive dynamic process scheduling
- seems particularly acute. As I understand it I have to assign percentage
- processor time to my background dos box and it doesn't waiver much from my
- fixed percentage assignment.
-