Date: 2012-07-13 13:56:47
I have to delete all the data about particular resources in the triplestore, and I'm finding that it's taking an inordinately long time. I have tried separate queries like:
<> ?p ?o .
<> ?p ?o .
and I have tried a combined query like:
?s ?p ?o .
?s ?p ?o .
?s = <> ||
?s = <> ||
Both of these seem to perform OK on my OWLIM-Lite instance but not on the OWLIM-SE instance. Could this difference between OWLIM-Lite performance and OWLIM-SE performance be down to a difference in the reasoning that's enabled (I have an empty ruleset on the OWLIM-Lite instance, but currently have the default owl-horst-optimized' on the OWLIM-SE instance)?
Is there an alternative method of deleting all the data about a particular resource that I should use?

asked 03 Apr '13, 10:34

Discussion-Board-Archive's gravatar image

accept rate: 30%

Date: 2012-07-13 19:07:12
Hi Jeni,
Another issue! Thanks for reporting it. Deleting statements is a bit 
more involved than simply  querying them, so there are several 
possibilities for what might be causing your problem. I'll let the 
developers comment on this first though.
By the way, there is something fundamentally different about OWLIM-Lite 
and OWLIM-SE in this regard:
In OWLIM-Lite, deleting even a single statement triggers the 
recomputation of all inferred statements, because there is no truth 
maintenance mechanism. In your case, you have inference turned off, so 
you won't see any problem. However, if you load a lot of statements in 
to OWLIM-Lite using the owl-max rule-set, you will find deleting 
statements is not so fast.
In OWLIM-SE, which scales to billions of statements, recomputing the 
whole inferred closure every time any statement is deleted is not 
practical. Therefore it uses a completely different mechanism that we 
sometimes call 'smooth delete'. There is still no truth maintenance 
information stored, but what happens is that some forward/backward 
chaining cycles are done to determine which inferences should be deleted 
whenever some explicit statements are retracted. This took a little 
while to get right, but it has proven to be very performant. It is 
possible that you could have uncovered a problem with this mechanism, or 
it could be that the poor delete performance has its cause elsewhere.
Again, I'll wait for the developers to comment on this, but one of us 
will get back to you very soon.
Have a great weekend,
Barry Bishop

answered 03 Apr '13, 10:34

Discussion-Board-Archive's gravatar image

accept rate: 30%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 03 Apr '13, 10:34

Seen: 903 times

Last updated: 03 Apr '13, 10:34

powered by BitNami OSQA