Gabriel NKUITE commented on Jan 9, 2014

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

In the document the following parameters are no more mentioned/used. Are they not needed for WP 8?

com.ibm.CSI.rmiInboundPropagationEnabled = false

com.ibm.CSI.rmiOutboundPropagationEnabled = false

com.ibm.ws.security.webInboundPropagationEnabled = false

Hunter K Presnall commented on Jun 24, 2013

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

MCacheMaxStreamingBuffer is the maximum size of a request that will be cached if that request has no Content-Length header. The larger 6MB value set in older versions of Portal which didn't have headers set in all cases. If everything in a customer theme has the correct header, then this value can be left at the default. We have confirmed there are no issues doing this on the default Portal 8.0 theme.

On the Windows systems tested in our lab, the 'groupAccess' parameter seems to be ignored. But you are correct about the System user when running as a service.

We will update these items in a future version of the guide.

Brad Thurber commented on Jun 13, 2013

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

Based on following the tuning guide on Windows, I would offer the following:

In the IHS tuning section, setting MCacheMaxStreamingBuffer to the suggested 6291456 caused Virtual Memory size to quickly rise to 2GB. Commenting this out (thereby taking the default of 100000) was much more manageable.

The Shared Class Cache section examples use the "groupAccess" parameter - which isn't available in Windows. Things get trickier when you are running as a service. As winodws doesn't use groupAccess, the cache gets created as the user running the jvm - which is probably SYSTEM. You need to login as SYSTEM (not administrator) to recreate the cache - which is possible but requires jumping through some hoops (Google for it).

Milton Alvarez commented on May 7, 2013

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

Shouldn't the title and attachment be clarified that it's for 8.0.0.1 also?

Hunter K Presnall commented on Feb 1, 2013

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

There is no need to run the chuser command if Portal is running as root. This has been clarified in the 1.1 version.

Shinobu Arita commented on Nov 26, 2012

Re: IBM WebSphere Portal V 8.0 Performance Tuning Guide

At Page 8, there is a instruction for AIX envirnment.

The following seems option setting to grant non-root user to use large page.

chuser capabilities=CAP_BYPASS_RAC_VMM,CAP_PROPAGATE $USER

Do we need to run this command in case that we start WP with root user ?

If not, please update the document as it is option.