Hi Jerven,
Seems I gave you a bum-steer. Sorry about that.
Nevertheless, we look forward to any other insight you can bring.
Thanks,
barry
On 27/07/11 10:30, Jerven Bolleman wrote:
Hi Damyan,
You where right in the end sorting the statements did not change a
single thing. Will keep looking for the source of the problems. Which
I now suspect is outside owlim itself.
The memory behavior is a bit suspicious and will have a look at that.
Regards,
Jerven
On 07/26/2011 02:47 PM, Damyan Ognyanov wrote:
Hi Jerven,
not sure if it would work - it all depends on the way you compare the
statements. But no matter how you actually do that comparison, the order
in which we index them will be different to that, since we use one that
is based on the value of the entity ID assigned to a particular RDF node
and it actually reflects the chronological order in which the nodes
appear in the data set ...
regards,
Damyan Ognyanov
Ontotext AD
On 26.7.2011 г. 15:08 ч., Jerven Bolleman wrote:
Hi Damyan,
Thanks for this information. I changed the way that I generate the
triples for insertion by owlim.
I read my raw rdf source in one thread generating statements.
The statements pass via blocking queue into a second thread which
inserts them via a sail connection into owlim.
I changed the blocking queue into a priority blocking queue.
With the following sorting. First sort on predicate then sort on
subject.
Is that the ordering that you would suggest or does an other one make
more sense?
The run is going to take quite a few hours so will let you know what
comes out of this tomorrow morning.
Regards,
Jerven
_______________________________________________
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
_______________________________________________
OWLIM-discussion mailing list
OWLIM-discussion@ontotext.com
http://ontotext.com/mailman/listinfo/owlim-discussion
