|
----- Original Message ----- From: srichter <srichter@mail.autocoder.com> To: <midrange-l@midrange.com> Sent: Wednesday, August 29, 2001 7:23 PM Subject: Re: Timeslices Hey Leif, The situation I have is with three interactive jobs that each runs for two hours (if alone). Every ten seconds or so, each job shows a screen with a progress bar. (Don't say that these jobs should run in batch). I just don't understand the behavior. I dont think timeslice matters any more. I work on a very fast 720 that uses the default qinter timeslice of 2000. 2000 milliseconds back in the s38 days meant something. Now, you can probably run many batch jobs with 2 seconds of cpu time. I am thinking of saying that activity level matters more than timeslice, that it might be too low and jobs that want to run have to wait to get into the activity level. But jobs run so much faster now, that they leave enter and leave the activity level so fast that the actual activity level never gets very high and jobs are never waiting to get into it. Steve Richter ---------- Original Message ---------------------------------- From: "Leif Svalgaard" <leif@leif.org> Reply-To: midrange-l@midrange.com Date: Wed, 29 Aug 2001 17:28:23 -0500 >I have noticed that (interactive) jobs with a small timeslice >are more "reactive" than jobs with a large timeslice. >This seems to indicate that the OS/400 is not "truly" >preemptive. Is this observation correct, or am I missing >something, or should I even know? >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.