On Jan 28, 2011, at 12:44 AM, Jerven Bolleman wrote: > I must say that SPIN is really fast. I now have 5 rules/spin constraints. And > in testing SPIN time is 20% of program time. The other 80% is mostly spent in > IO and triple generation.
BTW if most time is spent on IO operations, then you may want to convert to faster triple stores for those tasks. For example, Jena TDB is often a good choice when it comes to executing SPARQL queries fast. With other databases, each SPARQL query may result in many small round-trips to the database, slowing down performance significantly. TopBraid has some caches built-in, but those caches will not be available through the SPIN API out of the box, and I would recommend setting up a TDB as a (write-through) cache. Cheers, Holger -- 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
