Sorry, this is bl126.96.36.1991
what OS is your appserver ?
and you are using the 'performance commands' or the normal blcli ?
Thanks for your reply and sorry, we're using Red Hat Linux 2.6.9-67.
We are using the performance commands but at times we are using the normal blcli.
In some cases we have no choice but to use the normal blcli, i.e. through an integration pack from Opalis where using performance commands isn't an option. However, if we could set it up that by default only 1/2 gig is used, this would alleviate this problem.
the default is 256m iirc. if you edit the /usr/nsh/br/blcli file look for the Xmx parameter. you can change that to 256m or 512m.
for the performance commands the max heap should be hardcoded to be 256m - startup nsh and then run:
what does that show for Xmx ?
you may also want to look at the Xms setting which is the minimum heap size. if it's really consuming 1.5 gb on startup i think that may also be set high.
the question though is why was the heap raised ? it's possible that some command needs that much memory to operate in your workflows. if so it may be possible to raise the heap for only that command.
Cheers Bill, you're always a very helpful person!
I believe that we may have been told something incorrect or we had misunderstood.
It is set to 256 meg as per the default value you mention, not the 1.5 gig as I mentioned. Two values may be being confused here.
The appserver heap is probably 1.5g, which is ok.