[Mulgara-dev] XAFix Impl notes
David Moll
DMoll at viewpointusa.com
Thu Dec 14 14:41:12 CST 2006
It's been pointed out to me that I was mistaken, we're using a memory
size of 750MB for TKS2.1.
F:\Program Files (x86)\TKS21\jre\bin\java" -Xms750M -Xmx750M -server
-jar "F:\Program Files (x86)\TKS21\tks-2.1.jar" -k 192.168.10.205 -o
192.168.10.205 -d
That's on production. I'll test out Mulgara and get the -verbose:gc
output for doing a restore with the different JVM memory options. I
will check to see what sort of upper limit we are seeing with concurrent
sessions.
~Dave
-----Original Message-----
From: mulgara-dev-bounces at mulgara.org
[mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of Tate Jones
Sent: Thursday, December 14, 2006 3:33 PM
To: David Moll
Cc: mulgara-dev at mulgara.org
Subject: Re: [Mulgara-dev] XAFix Impl notes
I would certainly not increase the memory that high eg. Xmn and Xmx
to 3Gb. You are actually hurting the performance. It is probably
worst than the standard JVM settings. The triple store relies on
mapped i/o outside the JVM. By increasing the memory that high you
have removed the available memory from the OS. By setting the Xmn at
3Gb I believe you have immediately obtained 3Gb of memory via the
young generation. I maybe wrong here.
Please send me (tar or zipped) of the -verbose:gc output.
Been involved in many performance tuning projects, I would not
increase the Xmx above 1500mb. I would be very surprise if Mulgara
is using more than 256Mb with 50 concurrent sessions.
Please try -Xms 256mb -Xmx256mb and -Xms512mb -Xmx512mb with -verbose:gc
More information about the Mulgara-dev
mailing list