× 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: Re: Upgrade Options
  • From: Gary Feinstein <gfeinste@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 12 Feb 1998 10:04:57 -0500
  • Organization: Planet Hollywood International Inc.

Jeff,
        Thanx for the reply.  I pretty much figured the same thing regarding
the memory option.  I currently have 512Mg of memory which has very low
faulting rates in each pool.  Unfortunately, I think it would be real
tough trying to cost justify another processor into the machine at this
time.  We have only had the 400 for about a year and a half and it may
be too soon to hit the upper levels with a pricey upgrade.  While its
not URGENT, I did want to plan my upgrade options before it became a
problem.   

Gary

Jeff Carey wrote:
> 
> Gary Feinstein wrote:
> >
> > I am currently running a 510 with 512Mg of memory, 60 Gig DASD and 2143
> > processor.  At most, I have about 50 users on at the same time.  Lately,
> > some of my power users are running a number of resource intensive batch
> > jobs at the same time.  My quetion is:  What is the best was to upgrade
> > in order to get the most bang for the bubk.  Do I throw in another
> > processor (bringing me to 2 out of a total possible 4).  Or do I throw
> > more memory into the system.  I have heard that RISC is really greedy
> > when it comes to memory.  How can I test my system to see which is the
> > best option?
> > TIA,
> > Gary Feinstein
> > AS/400 System Administrator
> > Planet Hollywood International Inc.
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to "MIDRANGE-L@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
> > +---
> 
> Well, if you can, run one batch or a couple batch jobs at a time instead
> of all of them.  If you can't, run performance collection when the heavy
> batch jobs are running and model it with BEST/1 (part of Performance
> Tools/400).  Also watch WRKSYSSTS - are you getting a lot of faulting?
> can memory be moved from other pools to the pools running the batch
> jobs?  If all pool faulting is high, then more memory will help.  If
> not, a processor upgrade might help (multi-processor systems work great
> for batch throughput).
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---


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.