Hi Jack,
I have created an artificial set of 100k classes, all rdfs:subClassOf
owl:Thing to confirm some of the slowness that you are seeing. I can
confirm that you should switch the class tree to have rdfs:Resource as
its root as this will prevent all subclasses of owl:Thing from appearing
by default. You can reach this option from the drop down menu of the
Classes view - uncheck owl:Thing as root class. That should allow you to
open your file with reasonably speed and then close the (useless) class
tree before it drags down the system.
With 100k classes, it takes about 1 minute to open owl:Thing and I can
see in the Jave profiler that this is a general slowness of the Eclipse
platform's tree component as only a fraction of this time is spent in
TopBraid-specific code. But my question is why is your specific ontology
taking 20 times as long. Did you activate human-readable labels (if yes
please try switching that off)? What hardware are you using and do you
have enough memory?
Thanks
Holger
On 5/31/2014 7:45, Jack Hodges wrote:
Scott,
Thank you for the help!
I did as you suggested (a few times) and then closed and reopened the
model. Here is the timeline (just finished):
2:15 pm: Opened the model
2:20 pm: Get the "Applying default superclass inferences to class..."
message in the Progress Information dialog (in the end there were just
over 90,000 classes)
2:21 pm: Get the "Checking visibility" message in the Progress
Information dialog
2:23 pm: Get the "Showing model" message in the Progress Information
dialog
2:38 pm: Get the "Opening editor" message in the Progress Information
dialog
2:43 pm: Load complete
So there was (a lot of) improvement, but it is till taking almost 30
minutes to load. Is this the best I can expect or are there more
tricks I can apply?
Thank you!
Jack
On Wednesday, May 28, 2014 2:57:48 PM UTC-7, Scott Henninger wrote:
Jack; There are a number of models that fail to assert "root"
classes, i.e. all classes that are subclasses of owl:Thing. While
technically correct, these are difficult to process, as the system
has to find all of the class definitions that have no subClassOf
definitions. This is the "Applying Superclass Inferences" statement.
The way to speed this up is to assert these inferences, either in
the model or another import.
One way to easily assert the inferences is to choose Model > Open
with SWA Default Application in Composer. Again, this will take
some time, but in the end it will make the assertions and you can
save them so you do not have to do this in the future.
-- Scott
On May 28, 2014, at 3:32 PM, Jack Hodges <jhodg...@gmail.com
<javascript:>> wrote:
I added an import into a model I am constructing. This import is
the FMA (anatomy ontology) and has tens of thousands of classes.
It took a couple of minutes to add it. I later had to exit TBC
and when I reopened the application the Progress Information
dialog said the app was "Applying Superclass Inferences" for an
hour (I have since changed the preferences to suppress this
step). Then the Progress Information dialog told me it was
"Checking Visibility" which it did for another hour. I could not
find a preference to suppress this. Considering that it didn't
take much time to initially import the models, why would it take
so long to reload everything, and can I configure TBC to load
faster? Btw, the models just finished loading and its been a
couple of hours. Thank you anyone!
Jack
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include
Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid
Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
topbrai...@googlegroups.com <javascript:>
To unsubscribe from this group, send email to
topbraid-user...@googlegroups.com <javascript:>
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
<http://groups.google.com/group/topbraid-users?hl=en>
---
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to topbraid-user...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise
Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid
Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to topbraid-users+unsubscr...@googlegroups.com
<mailto:topbraid-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
