I have now managed to try your ontology (the github indeed shows me
20MB size, but when I clone the repository, I get only small files,
but the dropbox link works fine).
As I suspected, the main problem is caused by the transitive object
properties (there are 6 such axioms, if I comment them out, the
ontology is processed very quickly). Essentially, ELK computes the
whole transitive closure of the location graph. I managed to process
your ontology with 5GB of RAM given to java (but 4GB may work as well
since ELK shows me that it uses about 3.5GB of memory). This was done
using the command line client - for OWL API one probably needs to
allocate a little bit more memory.
Anyway, your ontology looks interesting, and given the statistics I
obtained, I think ELK should be able to do it within reasonable memory
limits. We will look at your ontology more closely if we can optimize
the memory consumption. Meanwhile, I suggest you to try a machine with
You said this is only a part of your dataset? What size is your full
dataset? Can you share it with us?
On Mon, Oct 21, 2013 at 6:00 PM, Lasitha Wattaladeniya