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



Depends on your workload & generation of CPU, of course, but for a
Power5/6/7 I would suggest a bare minimum of 8-10GB/CPU core. If you're
running workloads that are RAM-intense (Java, WebSphere App Server, etc.)
then shoot for 16+GB/core. If you're running lots of concurrent jobs, more
RAM is better since it will reduce paging.

On our two systems - a Power5+ and a Power6 - we've got 64GB RAM and 4
active cores so 16GB/core. It works well for our workload (JDE World,
EnterpriseOne, and supporting apps).

On Wed, Jun 6, 2012 at 1: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.
--
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 ...

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.