For SPARQLMotion, each module that executes in the script is timestamped in the Console view. For SPIN inferences, data on queries is shown in the error log (Window > Show View > Error Log). The function afn:now() gets the time (in milliseconds) of when a query starts, and could be used to define whatever benchmark you need.
The main performance rule for SPARQL queries is to reduce the number of matching triples as early in the query as possible. In particular, FILTER does not need to be at the bottom of a query (as seen on many examples), and will help performance when used to reduce matches early. Use ASK when you only need to know if a match exists, as it will terminate on the first query match. Post-processing, such as DISTINCT and ORDER BY will, of course, carry performance hits. -- Scott On Jun 25, 1:07 pm, Joe Eberle <[email protected]> wrote: > We are running a wide number of SPIN rules and are trying to optimize > performance. > > Is there a a console or trace mechanism that will help us profile the > performance of the inference engine and process? > > We need to perform benchmarks and break those benchmarks by > function. > > Thanks, > Joe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
