× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hey Leif,

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?
>
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.