× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Tom;

That is what I have always understood also, and the way I have my box set up at home but here I am just a lowly developer and the admin staff don't have a clue. We are having performance problems with our web services on a 12 way 570-MMA where I am running a 170 at home with no performance problems.
I double checked my box set up last night and I have QWAS6, QHTTPSVR, and QUSRWRK in a shared pool so my spidie sense was wrong. Now I get to have fun convincing admin to modify the development box to prove the viability of making the modifications before I can convince them to do it in production.

Thanks
Duane Chriten

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Wednesday, February 04, 2009 9:19 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Storage pools and QHTTPSVR and QUSRWRK subsystems

Christen, Duane J. wrote:

We currently have subsystem QWAS6 (Websphere 6.0 server) in its own storage pool, which has seemed to improved the performance of our web interactions. I would like to move subsystems QHTTPSVR and QUSRWRK to the same pool as QWAS6, but in the back of my mind is a warning that QHTTPSVR should stay in the *BASE pool.

Duane:

Unless you have QWAS6 running a private, rather than shared, memory pool, I can't think of any reason why you should have any work at all running in *BASE. QHTTPSVR and QUSRWRK, and others, doing active work in *BASE only makes things harder for any performance adjustments to happen.

IMO, the first thing to do on any system where performance monitoring will be done is to stop using *BASE for jobs. All jobs.

Let the system decide when *BASE should be used, e.g., perhaps via QTSEPOOL. But don't route them there yourself without _expecting_ general performance to suffer with no good explanation.

(Routing to *BASE "yourself" means not changing IBM's default subsystem descriptions for pools and routing entries and prestart
entries.)

As usual, here's hoping someone adds something authoritative. My opinion is purely from reading over the years about work management and performance maintenance.

Tom Liotta

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
253-479-1416
Fax 253-872-7904
http://www.powertech.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.