Arthur; I'm afraid there isn't an easy explanation for this. Since you re-load a file, caching should not be an issue. I take it this is a repeatable behavior, and that the >40x speedup was only on the data with 1000 "families"?. Would it be possible to share the rules or some variation thereof to further analyze what may be going on? Also let us know what the other details are, such as heap space, number of triples/file size, etc.
-- Scott On Oct 18, 3:35 pm, Arthur Keen <[email protected]> wrote: > I did some informal testing of SPIN versus Jena rules performance in > TopBraid Composer 3.3.2. I created a schema model, and instance data model, > and separate models containing equivallent Jena and SPIN rules to infer > familial relationships. I used a construct query to create synthetic family > data (without saving). I ran tests on 10, 100, 1000 families (without > saving) and collected statistics. For 1000 families SPIN at 40s was 5% > faster than Jena . I had some issues with Composer and restarted it and > accidentally saved my synthetic data after being prompted. After the > restart and reload of the models, the same inferences (SPIN and Jena Rules) > on 1000 families took less than a second, i.e., > 40x speedup. I am trying > to understand if this is a TopBraid or Jena phenomenon and what caused the > speedup and how I can leverage it when doing inferences on freshly created > information. > > Thanks > Arthur -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
