|
Bryan, Replies inline: > 1) Should I spend the time to pursue the root cause of this? We have > had no performance issues since we upgraded from a 620-2179 to an > 820-2395-1523 last fall. 1 - The consequences of exceeding your interactive threshold are roughly equivalent to maxing out an entire system, with the exception that your batch should continue without too much disturbance. All interactive work will perform like molasses in winter until you get the work back below the threshold. No permanent damage will be done. You need to decide whether it's worth the effort. > 2) Could this be caused by queries? We have over 6,000 queries and 275 > users on our box and most users run their queries interactively. 2 - Absolutely. Running queries interactively in a good way to burn CPU. Considering that you have more processor power available in batch, you might be able to get faster throughput in batch. In addition, you could also attain a higher level of ideological purity :). > 3) Could this be caused by SQL? We recently started some applications > that use SQL through ODBC. I turned the SQL monitor in OPS NAVIGATOR on > for > a few hours one day and did an analysis but did not find anything > significant. 3 - No, your ODBC connections will process in the batch CPU allocation. > Thanks in advance for any replies. > > > Bryan Burns
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.