#2987: Tune or document tuning of Globus 4

This ticket is marked as priority 4, but we might drop it to priority 3.
We'll see.

We should consider helping users tune WS GRAM, or documenting how they
can do it. Globus has provided some documentation:
http://www-unix.globus.org/toolkit/docs/4.0/execution/wsgram/WS_GRAM_Performance_Guide.html

1. Set max heap size to 1GB

Current value ($VDT_LOCATION/setup.*sh) is
GLOBUS_OPTIONS "-Xmx512M"
should be
GLOBUS_OPTIONS="-Xms256M -Xmx1024M"


2. Instead FD limit to 16,384

Platform dependent; possible can workaround by putting a wrapper around
the executable.


3. Non-NFS recovery directory


Site-specific. We could do something clever like setting it to /tmp,
but we might end up with users accidentally or intentially stepping on
each other's files.


4. Increase thread limits

Current value in globus/etc/globus_wsrf_core/server-config.wsdd:
<parameter name="containerThreads" value="2"/>
<parameter name="containerThreadsMax" value="20"/>
Desired value:
<parameter name="containerThreads" value="20"/>
<parameter name="containerThreadsMax" value="50"/>
<parameter name="containerThreadsHighWaterMark" value="10"/>


5. EnableLocalInvocations

Change around line 320 of globus/etc/gram-service/jndi-config.xml
BUT WS-GRAM and RFT must be in the same container. Is this true? Can
it/should it be?


6. Decrease thread limits (see also #4)

Limit does not appear to be this high. Perhaps was local tuning?


7. Decrease max_active_allowed
Line 11 of ./globus/setup/globus/setup-rft.pl
< my $max_active_allowed = '100';