RE: Database server jobs and SQL tuning

At 12:09 05/17/2000 , Dan Bale wrote:
>Found a reference to this in a thread named "QZDASOINIT and ODBC
>performance", but the only suggestion was to change the time slice to 200
>and the run priority to 50.  I'm not sure how lowering the time slice from
>2000 to 200 would increase speed.  Anybody?

Changing the timeslice in this way will not improve the performance of your 
queries. It will, however, improve the overall performance of all of the 
other jobs on the system, which would suffer if you didn't change it. That 
timeslice was appropriate on CISC systems. IMHO, it is no longer. IBM has 
never updated their default configurations to reflect the improved 
capabilities of the hardware. You can divide the timeslice by 10 in all of 
your classes of service and the hardware will be more tolerant of CPU hogs 
like ODBC, and provide better service overall. As an aside, I have recently 
been through a situation where ODBC usage increased dramatically. Seagate 
Info was adopted as a corporate reporting tool. A CPU that showed peak 
utilization of 30% with interactive and traditional batch work suddenly 
required an upgrade. That upgrade provided a CPW increase of (I think) 2.5 
or 2.8 times. That was sufficient to handle the ODBC workload. Be prepared.


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
+---