WAS 5.1 Express Performance -- WEB400

× 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.

Subject: WAS 5.1 Express Performance
From: Dave Reiher/prairiefarms <DReiher@xxxxxxxxxxxxxxxx>
Date: Wed, 24 Aug 2005 08:58:33 -0500
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Anyone have any thoughts or know of any good resources on fine tuning WAS 
5.1 Express Application server performance?

I am running iSeries for Web on a small partition here, in my config for 
iSeries for Web I am redirecting to another AS400 off site. It just seems 
to run a little bit slow for our folks in the field. Is there anything I 
can do to fine tune the performance? Would throwing more resources at my 
partition do any good? The performance doesn't seem to take a hit on the 
400 partition except when starting or stopping an instance. I hate buy 
more memory or allocate more only to infd out it doesn't do me any good.

Any thoughts??

    Dave Reiher
    System Analyst
    Prairie Farms Dairy - Corporate
    Ph: 217.854.2547 ext. 254
    dreiher@xxxxxxxxxxxxxxxx

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.