|
Im with Scott on this one. Database server jobs will use a lot of memory if there is a lot of remote database access going. >From what i have seen in the past, the database server jobs bottleneck is usually memory, so either allocate some from subsystems that dont need it, or buy some more. Try and use WRKSYSSTS to review the level of paging. If that does not tell you much, configure the Database server jobs to run out of their own starage pool, then you can see how much paging and faulting is happening for them.
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.