Hi Steve,
On 2/10/12 1:35 PM, Stephen Bayliss wrote:
I was hoping to supply triple counts, but executing any SPARQL queries
(from the Stanbol SPARQL endpoint) on the above is triggering an out
of memory exception - do you have any suggestions on this? (I seem to
recall that you anticipated that there was likely to be an issue here.)
Actually I thought that endpoint wouldn't consider those graphs at all.
Have you tried using the Clerezza Java API by parsing the query via the
@Reference QueryParser and issuing it via TcManager.executeSparqlQuery() ?
Confirmed this is occurring with the above graphs. These are RDF graphs in
SKOS format, so you should easily be able to find some data to test with (eg
fromhttp://www.w3.org/2004/02/skos/).
Now, I'll need the help of Clerezza and fellow Stanbol developers on
that. I would guess that calling
mgraph1.addAll(mgraph2)
when the two MGraphs are both managed by the TcManager and the same
bound TcProvider, will NOT double memory usage. If that is so, you would
as a matter of fact be having one graph with multiple names.
@Reto / other Clerezza heads : can you confirm/refute this intuition?
For reference, the problem is described in the comments of
https://issues.apache.org/jira/browse/STANBOL-426
On a side note, in order to analyse this thoroughly : what is the best
tool for monitoring memory usage by Java objects in an Eclipse+Maven
environment, which can also run during JUnit test via Eclipse ? Are we
still with TPTP ?
Best Regards,
Alessandro
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"As for the charges against me, I am unconcerned. I am beyond their timid, lying
morality, and so I am beyond caring."
(Col. Walter E. Kurtz)
Not sent from my iSnobTechDevice
