|
At 10:52 09/13/1999 , Larry Bolhuis wrote: >Dale, > > I have played with moving this job around with little ill effect. >Two of my customers use this job very heavily. We moved the jobs to >their own memory pool at a specific execution priority. This allowed >the real users (green screens) to out prioritize them at the same time >as not fighting them for memory (this was the biggest problem as the >QZDASOINIT tasks would often swell to well over 10MB PAG size). It >did slow the ODBC jobs a bit but allowed the rest of the system to run >more smoothly. We've done this also, but found we also needed to decrease (all) time slices from the shipped values by a factor of 10 on a single processor S30. ODBC requests now run in their own subsystem at priority 50 with a timeslice of 200 and all is reasonably well. We need a processor upgrade though. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.