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



With IBM i 7.1 I start first with 4GB as a base even with a 0.1 processor partition, this is a decent starting point.

Then look at customer workload. For traditional workload (RPG/Cobol and green screen) I would agree with the 24GB to one CPU below as a reasonable number. Of course YMMV as you may have a larger number of interactive users or perhaps use lots of sessions or even group jobs. More users and more jobs = add memory.

If you're doing significant Web, or Java, or PHP, or SQL on the machine then start by doubling the 24GB Suggestion.

Also remember to round up - memory is LOTS cheaper than CPU and adding more often requires you pull smaller dimms leaving them on the workbench in order to put in larger new ones.

- Larry "DrFranken" Bolhuis

On 6/6/2012 2:06 PM, lketzes@xxxxxxxxxxx wrote:
Does anyone know of a Best Practice ratio or a general opinion of CPU to
Memory ratio. Someone from IBM suggested 24:1.


Thoughts?


Larry Ketzes
Lead Enterprise Infrastructure Engineer
lketzes@xxxxxxxxxxx
302-594-2146
The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.