[Pellet-users] Examples of When Pellet Runs Slowly

[JPQ]

> (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.)

That was me. In fact, at the very beginning of that email, I stated the
following. "This post was prompted by a post I made yesterday. The setup is
somewhat similar, but the subject matter is different."

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

Granted. I had posted a couple of Pellet-related questions on the TBC list
in the past. They were addressed, but I was asked to post them here. Thank
you for answering the question. I'll certainly have to look at Pellet and
the OWLAPI independently.

> 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.

No disrespect intended.


Cheers,

Anthony

On 3/25/08, Kendall Grant Clark <kendall at clarkparsia.com> wrote:
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.owldl.com/pipermail/pellet-users/attachments/20080326/6b85de1b/attachment.htm