On 12/11/12 17:37, Federico López wrote:
Well...
I'm using this command for run fuseki server,
java -verbosegc -XX:+PrintGCDetails -Xms1024m -Xmx2048m -XX:PermSize=1024m
-XX:MaxPermSize=2048 -jar fuseki-server.jar --update
--loc=/home/oscaroca/tdb/ /tdb &
And then I'm run several set of querys (about 100 each time) from Java via
ARQ, in average this returns resulsets of more or less 10 results/query
each time. It works fine and very quickly but the use of memory grows in
every set of query and never goes down. Until the program stop answering
the requests from ARQ. I was doing this in Windows 7 and i didn't have this
trouble before. But when I use Fuseki in Debian 6.0 the JVM does'nt release
the memory to de OS, it seems like never calls the Garbage Collector. I
don't know what to do, ¿Someone has used Fuseki on Debian 6.0 amd64 before?
We run on various linix flavors - the nearest being ubuntu.
The size of the process will not decrease and in fact will increase as
more heap is used, until a incremental or major GC happens.
What GC logging do you get?
If it get near to full, the GC can go mad (takes more time than real
work). Oddly, a little less or a little more heap canmake the problem
go away.
What else is running on the machine? If you look at the system monitor,
how much of RAM is in use? (caution TDB maps files which affects RAM
usage reports).
If you have a script that will provoke the scenario< i'll try to run it
here but I need a DB and some queries to simulate the situation.
Andy
2012/11/12 Andy Seaborne <[email protected]>
On 12/11/12 15:44, Federico López wrote:
I'm runing Fuseki Server 0.25 using Debian 6.0 amd64 with 4gb of RAM. I'm
using open-jdk.
I use this command for Fuseki server execution:
java -verbosegc -XX:+PrintGCDetails -Xms1024m -Xmx2048m -XX:PermSize=1024m
-XX:MaxPermSize=2048 -jar fuseki-server.jar --update
--loc=/home/oscaroca/tdb/ /tdb &
Fuseki (JVM) is not releasing the memory that use in all kind of operation
and get stuck after execute a number of operations.
As far as I know, Java doesn't release memory back to the OS. Once the
heap has been grown and caused the process to grow to some size, the JVM
remains at that size.
Do you have a complete, minimal example of what you are doing?
Andy
¡Please Help!
