[Pellet-users] Examples of When Pellet Runs Slowly

[Kendall Grant Clark]

Excerpts from jpq.semantics's message of Tue Mar 25 15:39:40 -0400 2008:

> The items marked with asterisks indicate those variations which had Pellet
> running very slowly. Pellet (Pellet library plug-in, version 1.5.1) was run
> within TopBraid Composer (version 2.4.2). At most I waited approximately one
> hour to allow Pellet to complete its inferencing on the marked items.

We don't support TopBraid Composer on this list. You're better off
asking TopQuadrant about it. 

The way they use Pellet internally -- via Jena, the last time we
checked, rather than OWLAPI -- is not recommended or ideal, so we
can't say anything about performance problems encountered when using
Pellet in ways we don't recommend.

If you can repeat yr observations with Pellet directly, we'd be happy
to consider yr bug report, ideally with minimal code and ontology
sufficient to demonstrate the problem. (I see that someone with the
same email address posted about a seemingly related issue yesterday,
but that was about Pellet semantics, not peformance, so I won't make
any assumptions about a connection.)

Finally, a word about "best practices" in the context of this mailing
list: we are very much not willing to give free tech support to people
who do not identify themselves by name in email. Other people on this
list may be willing to help in that circumstance, but we aren't among
them. FWIW. :>

-- 
Cheers,
Kendall