OBO-Edit:Reasoner Benchmarks

From GO Wiki
Jump to navigation Jump to search

PRELIMINARY benchmarks for various reasoners vs various ontologies.

There is an unashamed GO bias here. We are evaluating with an eye to the project growth of GO particularly w.r.t both internal and external. We also care about database queries as well as ontology maintenance.

OBO-Edit Native Reasoners

oboedit_fcr

OBO-Edit:Forward Chaining Reasoner (LPR). Fast, but only uses the following rules:

  • Transitivity
  • Propagation over/under is_a
  • Intersection_of (aka xps)

John wrote this first in OE1, and then abandoned it. Can still be used for so-xp, and is suitable for certain purposes such as finding trivial redundancies by transitivity, but not recommended in general

oboedit_lpr

OBO-Edit:Link Pile Reasoner (LPR). Successor to FCR.

Rules:

BUGS: there are certain edge cases involving sub-relations and transitivity that do not work. This bug was discovered after John left. The code is difficult to maintain so this reasoner will eventually be abandoned in favour of the RBR (Developer notes: this appears to be due to the fact that sub-relations are computed on the fly rather than cached)

oboedit_rbr

OBO-Edit:Rule Based Reasoner (RBR). Successor to LPR.

The internal design of the RBR is highly simplified compared to the LPR. It was written entirely by cjm. Note the profile is the same as for the LPR, however, the LPR bug does not arise due to the design of the RBR.

Note that the RBR is currently slow for incremental reasoning. This is because it checks all links after any links are added or deleted. This can easily be fixed in future versions. When it is, the LPR will probably be retired altogether.

OWL/DL reasoners

OWL Reasoners are superior to OE reasoners in that they can make use of more expressive constructs, such as complementOf (negation) and universal restrictions (all-only links). However, these constructs are not currently permitted in the OBO 1.2 language.

Some OWL reasoners only recently included transitive_over and arbitrary Relation_composition. They do not allow relation intersections.

Note that OWL reasoners will not allow you to ask questions of the form "what is the heart ventricle part_of?". To allow this we perform an extra step of materializing all transitive relation x class pairs (e.g. "heart part"). This leads to worse performance.

The two main open source OWL reasoners are FaCT++ and Pellet.

Note: even though the table below gives the suffix ".obo", each reasoner was executed on an owl file. These were generated by go2owl whenever the native form of the ontology is obo

owlapi_pellet

Pellet executed via the OWLAPI (1.2)

owlapi_pellet_mr

As above, with all class x relation pairs materialized.

owlapi_factpp

FaCT++ executed via the OWLAPI (1.2)

owlapi_factpp_mr

As above, with all class x relation pairs materialized.

pellet

Pellet 2.0 executed directly

hermit

Hermit 0.9.2 executed directly.

Note that hermit does not support object property chains -i.e. transitive_over or arbitrary Relation_composition. It will fail on any ontology that includes these. This means a lot of entries are blank.

oboedit_pwr

OBO-Edit pellet-wrapped reasoner. Pellet, executed with OE using a java object level bridge. Performs the class x relation materialization.

Needs updated to the latest Pellet API. May be discontinued in favour of an OWLAPI bridge

Database Reasoners

These reasoners use essentially the same procedure as the oboedit RBR. However, inferred links are backed by a relational database rather than in-memory. As such they tend to be slower, but are not-memory bound. These are also a good choice when the inferred graph needs to be stored in a database, to allow for advanced queries on annotations.

obdsql

Runs off of the OBD SQL schema. See OBD

Uses: Postgres 8.3

  • Transitivity
  • Propagation over/under is_a
  • Subrelations
  • Intersection_of

godb

This is used when loading ontologies into the GO Database. See Transitive_closure

Uses: MySQL 5

Relatively limited set of rules:

Will be extended in future

blipkit

Backed by a prolog database. This is the same reasoner used in obol.See blipkit home page

Results

Availability

See reasoner-benchmarks for the raw data.

Ontologies Used

TODO: show expressivity of each

The following ontologies were used:

Preliminary Benchmarks

Blank = program did not complete in allotted time or ran out of memory (note: a few blanks remain to be filled in, programs did not complete for external reasons, this is PRELIMINARY!!)

ONT hermit oboedit_fcr owlapi_pellet_mr owlapi_factpp oboedit_lpr oboedit_rbr obdsql owlapi_factpp_mr owlapi_pellet pellet godbsql blipkit
DC_CL 0.154 0.096 3.370539 0.352756 0.271384 0.101434 21 0.334486 3.700291 0 2 0.04
bp_xp_cc 13.476 113.021307 46.33769 1668 1540 80.96
bp_xp_ch
bp_xp_cl 13.589 84.450377 49.550078 1774 1612 89.41
bp_xp_u 14.096 102.442893 52.879202 2043 1545 86.89
caro 0.038 0.018 0.082236 0.016301 0.031378 0.027466 0 0.036096 0.167044 0 0 0.01
cc_xp_i 13.36 65.882047 289.564573 1573 1407 67.05
cc_xp_p 0.92 161.486508 19.044575 1.914166 148 1 68 3.59
cell 0.212 0.391 1.700208 0.090183 2.024176 1.039019 32 7.025427 1.459531 0 47 1.14

Methods

The reasoner-benchmarks.pl script was used.

The times above represent actual reasoning time (in seconds) as reported by the reasoner itself. It should exclude time for program to load etc.

4gb OS X, 32 bit java for OE, java -Xmx2048m

Standard oboInOwl conversion was used for obo ontologies when running with owl reasoners. For OWLAPI tests a custom simple runner was written, see: OWLReasonerRunner

Retrieved from "https://wiki.geneontology.org/index.php?title=OBO-Edit:Reasoner_Benchmarks&oldid=16927"