|
> We have the QINTER class set to a timeslice of 50. If the average interactive program naturally reaches a wait state (i.e. waiting for an AID key to be pressed) before 50 milliseconds, then your timeslice setting may be fine. Actually 50 milliseconds is probably fine on today's hardware. I see that one of my 5250 programs uses about 25 milliseconds on a model 170-2290 each time the PageUp key is pressed while paging through a subfile. On a model 800 the same program would probably only use about 3 milliseconds of CPU before naturally entering a wait state. The timeslice is more relevant to applications that use a lot of CPU time before reaching a wait state on their own. Where an RPG program using the 5250 interface may need only 25 milliseconds, a comparable Java Servlet may require 600 milliseconds, so swapping the Servlet it in and out of the CPU at 50 milliseconds intervals, would lead terrible response times. Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
