All BladeLogic environments are different, therefore I would advise benchmarking these settings for yourself. You can adjust the JVM heap used by the JLI by editing the shell script which starts jython. In my environment it's called "bljython." Note that you can easily use multiple scripts, just adjust the scripts which call bljython accordingly.
Here's my benchmark. It is very simple - it just pulls a list of servers, and times how long it takes to execute via Java's runtime library. (If I'm not mistaken, the memory listed in the app server logs is for the app server JVMs, not the JLI JVM.) You could substitute any command which you like, or a whole suite of commands. I chose this command because it was causing issues in my environment, failing due to a lack of memory.
The first line in this jython script should point to your customized shell script. IE, create two or three shell scripts, each with unique Xmx and Xms settings, then run the benchmark for each setting. This should help you determine what setting gives you the best balance of speed and memory usage.
#! /usr/bin/env /bladelogic/nsh/br/bljython
import bladelogic.cli.CLI as blcli
from java.lang import Runtime
cmd = 
maxMemory = (Runtime.getRuntime().maxMemory()/1048576);
freeMemory = (Runtime.getRuntime().freeMemory()/1048576);
allocatedMemory = (Runtime.getRuntime().totalMemory()/1048576);
logtime2=time.strftime("%a %m/%d %H:%M:%S",time.localtime(time.time()))
print "JVM Free Memory = %sM, allocated memory = %sM, maximum memory = %sM.\n" % (freeMemory, allocatedMemory, maxMemory)
print "Program started at %s; this command finished at %s." % (startTime, logtime2)
logtime1=time.strftime("%a %m/%d %H:%M:%S",time.localtime(time.time()))
cli = blcli.CLI()
blcliResult = cli.connect()
for i in range (5):
What OS and Arch were you running this on, and what arch was the jvm?
so are you setting both Xmx and Xms to 2g?
the only problem w/ 2g is that if you spin up a bunch of blcli (like a nsh job) you could hoze your appserver, though the same is possible w/ the 256m heap, it would just happen a little faster