GraphDB-SE Performance Tuning

compared with
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (11)

View Page History

<wayne_rooney> <foaf:name> "Davenport"^^xsd:string .
<wayne_rooney> <foaf:name> "Wayne Rooney" .
<Reviewer40476> <rdf:type> <MyClass> .
<Reviewer40478> <rdf:type> <MyClass> .
<Reviewer40480> <rdf:type> <MyClass> .
<Reviewer40481> <rdf:type> <MyClass> .
{noformat}When using the {{owl-horst}} rule set the removal of the statement:
{noformat}<wayne_rooney> <foaf:name> "Davenport"
{noformat}<wayne_rooney> <foaf:name> "Wayne Rooney"{noformat}
{noformat}will cause the following sequence of events:
x a y - (x=<wayne_rooney>, a=foaf:name, y="Davenport") y="Wayne Rooney")
a rdfs:domain z (a=foaf:name, z=owl:Thing)
The user instructs GraphDB that the transaction is a system transaction by including a dummy statement with the special schemaTransaction predicate, i.e.
_:b1 <> "" _:b2
This statement is not inserted in to the database, rather it serves as a flag that tells GraphDB that it can ignore the read-only flag for imported statements.
h1. Optional indices

h2. Predicate lists

GraphDB-SE uses a number of query optimisation techniques by default. These can be disabled by using the {{enable-optimization}} configuration parameter set to {{false}}, however there is rarely any need to do this.
See [GraphDB-SE Explain Plan] for a way to view query plans and applied optimisations.

h2. Caching literal language tags