You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, every time a Knowledge Interaction is activated the ReasonerProcessor is recreated and part of this process is the costly graph pattern matching algorithm. Under certain circumstances (i.e. when the network is stable), the ReasonerProcessor can be reused which improves the performance considerably.
Doing a quick and dirty and naive implementation of this in the InteractionProcessorImpl where we reuse the ReasonerProcessor object when encountering the same KnowledgeInteraction object shows that for the TestPostReactPerformance test where the same knowledge interaction is repeated 1000 times it improved the performance per interaction from 9.5ms to 4.5ms. So, almost twice as fast.
So, this is an obvious place to further improve the performance of the knowledge engine when the network is (quite) stable.
The text was updated successfully, but these errors were encountered:
Currently, every time a Knowledge Interaction is activated the
ReasonerProcessor
is recreated and part of this process is the costly graph pattern matching algorithm. Under certain circumstances (i.e. when the network is stable), theReasonerProcessor
can be reused which improves the performance considerably.Doing a quick and dirty and naive implementation of this in the
InteractionProcessorImpl
where we reuse theReasonerProcessor
object when encountering the sameKnowledgeInteraction
object shows that for theTestPostReactPerformance
test where the same knowledge interaction is repeated 1000 times it improved the performance per interaction from9.5
ms to4.5
ms. So, almost twice as fast.So, this is an obvious place to further improve the performance of the knowledge engine when the network is (quite) stable.
The text was updated successfully, but these errors were encountered: