On 11/12/2014 0:23, Nikolaos Beredimas wrote:
So how would you think a SPIN API based solution would perform? Would
the answer come in the order of seconds or minutes? (for reference my
Drools based current implementation responds in the order of hundreds
of milliseconds in a modern workstation).
The current SPIN API will be much slower than Drools. I guess Drools has
a proper RETE engine, which knows which rules need to fire when. The
SPIN API currently only implements a brute-force approach in which it
may need to touch every rule to see if they fire. It doesn't prebuild a
helper data structure beforehand.
Instead of having tens of thousands of similar rules, would it be
possible to rewrite the rules so that they are more generic, so that you
would only need to run three rules?
HTH
Holger
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
