<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://3635/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>We all know what they say about premature optimisation, so maybe it would be worth stating your performance goals? It might help with establishing which direction the optimisations should go. And also whether such optimisations are even worth trying to achieve.</div><div><br></div><div>In a knowledge base with a reasonable number of rules, and especially if a number of facts need to be derived on start-up, the technique Wolfgang mentions with a long-running session is what I have found tends to give me the best performance. i.e. For each incoming request: insert, fire, retract, fire. Obviously it depends on your rules, but sub-millisecond evaluations are quite achieveable (~20 microseconds is the fastest I have achieved so far). Which takes me back to the question of what throughput do you need to achieve? And how bursty are you expecting it to be?</div><div><br></div><div>Of course, if there is no dependence between evaluations (i.e. you're not accumulating transaction values or anything like that) it's pretty simple to set up a queue of requests and a pool of stateful sessions, so it's not that much wasted effort if you don't need it.</div><div><br></div><div>Steve</div><div><br></div><div><br></div><br><div><div>On 7 Feb 2013, at 18:05, "Cotton, Ben" <<a href="mailto:Ben.Cotton@morganstanley.com">Ben.Cotton@morganstanley.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><br class="webkit-block-placeholder"></div><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 14pt; font-family: 'Lucida Console'; text-indent: -0.25in; "><span style="font-family: Wingdings; "><span>Ø<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "><span class="Apple-converted-space"> </span></span></span></span>Maybe you just need a StatelessKnowledgeSession (you're using this term in a later mail), that, when used in *sequential mode* is faster.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><span style="font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">But the fear we have here is that the backing queue of simultaneously arriving facts could back up if we process in synchronous sequence. We are willing to trade off an individual fact being processed more slowly, if we can simultaneously process many facts.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><span style="font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><br>As you point off, the pattern that wins the “sequential v. parallel” bake-off is TBD.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><span style="font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">-----Original Message-----<br>From: <a href="mailto:rules-users-bounces@lists.jboss.org">rules-users-bounces@lists.jboss.org</a> [mailto:rules-<a href="mailto:users-bounces@lists.jboss.org">users-bounces@lists.jboss.org</a>] On Behalf Of Wolfgang Laun<br>Sent: Thursday, February 07, 2013 12:50 PM<br>To: Rules Users List<br>Subject: Re: [rules-users] ambition = ThreadPoolExecutor delegating to KBPool(s) & KSPools(s)<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">KnowledgeSessions are created from a KnowledgeBase, and they are independent from each other, even when they come from a single KnowledgeBase. So I don't see the need for 24 KBases.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">You've referred to "fireAllRules()", which isn't available with a StatelessKnowledgeSession. Maybe you just need a StatelessKnowledgeSession (you're using this term in a later mail), that, when used in *sequential mode* is faster. Otherwise, disposing a StatelessKnowledgeSession after processing each fact may not be faster than simply retracting the fact from a StatefulKnowledgeSession, which would prepare it for the next task, and not cause everything to go through GC.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">Just benchmarking will tell you what is best for your scenario.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">-W<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">On 07/02/2013, Cotton, Ben <<a href="mailto:Ben.Cotton@morganstanley.com" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">Ben.Cotton@morganstanley.com</span></a>> wrote:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Thanks Jeremy. Just finished watching your referenced video "Drools<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> & Large Data Sets Workshop" - no doubt about it, people are explicitly<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> using this pattern (Pool,Queue,Delegate,Callback) w/in Drools to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> achieve higher concurrent "simultaneous fact arrival" transaction throughput, and scale.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Especially appreciate your comment re: managing Runnables' callbacks<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> w/in the proposed framework... we indeed have to be careful here, and<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> will re-factor or design accordingly.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> From:<span class="Apple-converted-space"> </span><a href="mailto:rules-users-bounces@lists.jboss.org" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">rules-users-bounces@lists.jboss.org</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> [<a href="mailto:rules-users-bounces@lists.jboss.org" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">mailto:rules-users-bounces@lists.jboss.org</span></a>] On Behalf Of Jeremy Ary<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Sent: Thursday, February 07, 2013 12:08 PM<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> To: Rules Users List<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Subject: Re: [rules-users] ambition = ThreadPoolExecutor delegating to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> KBPool(s) & KSPools(s)<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Yep, that all makes sense for the more elaborated context. Sounds like<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> you're working with a model wherein you needn't concern yourself with<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> relational logic between instances, so I think the value of splitting<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> sessions over threads with a multi-consumer queueing setup could allow<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> you the opportunity to async your process with better throughput. What<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> you and I propose differs only in high-availability and scalability of<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> the input stream (potentially arising from throttling to a single<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> instance responsible for maintaining task scheduling and executor<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> lifecycle), offering an ability to recover should you lose your<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> application containing pooled tasks and allow for smaller pool sizes<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> to maintain (pull only as needed/desired from queueing and adjust that<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> capacity on the fly for high-usage times such as first thing in the morning).<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Semi-related I just found a video about a large-scale operation that<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Alexandre Porcelli created that might be of some interest to you.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="http://vimeo.com/27209589" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">http://vimeo.com/27209589</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> My only other thoughts going into it is consider some different<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> approaches for the scheduling mechanism given that, as I've had the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> unpleasure of discovering before, callbacks from runnables can be fun<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> to keep up with of you're dependent on them, so fire-and-forget vs.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> results synchronicity can make a difference in the mechanism you<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> choose to maintain your tasks and pools.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Regards,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Jeremy<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> On Thu, Feb 7, 2013 at 10:47 AM, Cotton, Ben<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> <<a href="mailto:Ben.Cotton@morganstanley.com%3cmailto:Ben.Cotton@morganstanley.com" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">Ben.Cotton@morganstanley.com<mailto:Ben.Cotton@morganstanley.com</span></a>>> wrote:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Thanks for your response, Ary.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> It is much more about accommodating high-frequency and throughput. <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> The rules are ZERO sensitive to time and order - they are rendered 1x<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> at start of day. They are exceedingly complicated, and there are lots of them ...<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> but once they are bound to a KB nothing changes about them for the whole<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> day. When we put a fact on a KS.fireAllRules() task the rendered decision<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> is idempotent wrt to rules' firing(s) order.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Also, all arriving facts are immutable and all sessions are stateless,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> so we kind of have ignored CEP (seeing it as more appropriate for a<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> long-living ecosystem of continuously mutating facts).<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Effectively, we want a "small, simple, safe, speedy" body of<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> operations on "complex, cumbersome, concurrently-arriving, constant" facts.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> From:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="mailto:rules-users-bounces@lists.jboss.org%3cmailto:rules-users-bounces@lists.j" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.j</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> <a href="http://boss.org">boss.org</a>><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> [mailto:rules-<a href="mailto:users-bounces@lists.jboss.org">users-bounces@lists.jboss.org</a><mailto:rules-users-bounces<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> @<a href="http://lists.jboss.org">lists.jboss.org</a>>]<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> On Behalf Of Jeremy Ary<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Sent: Thursday, February 07, 2013 11:32 AM<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> To: Rules Users List<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Subject: Re: [rules-users] ambition = ThreadPoolExecutor delegating to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> KBPool(s) & KSPools(s)<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Are you in a place where your rules have become sensitive to time and order?<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> If so, have you considered CEP? If it's less about that and more about<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> getting the work done ASAP, you could also investigate a messaging<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> integration pattern to assist with all the pooling/throttling/queueing<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> needs you've mentioned.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> On Thu, Feb 7, 2013 at 10:04 AM, Cotton, Ben<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> <<a href="mailto:Ben.Cotton@morganstanley.com%3cmailto:Ben.Cotton@morganstanley.com" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">Ben.Cotton@morganstanley.com<mailto:Ben.Cotton@morganstanley.com</span></a>>> wrote:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Let's say that a start-of-day, every day, we generate a giant 2,000+ <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> rule .DRL, that we then use to construct into a single run-time<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> KnowledgeBase reference. We then construct a single run-time<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> KnowledgeSession reference (also at start of day). Throughout the day, all day, facts "arrive"<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> asynchronously into our expert system. When a fact "arrives", we<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> synchronously place the fact onto our single KS and call<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> .fireAllRules(), which in turn synchronously outputs answers that<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> satisfy our "what's the next step?" decision requirements.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> We have this working very well, but we have the ambition to achieve more.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> We want to attempt to scale this solution to accommodate the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> high-frequency simultaneous "arrival" of many facts. We have at our<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> disposal a 24xCPU 128 gb Linux-based compute resource (nice, right?)<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> ... so, ideally, we have the ambition to potentially accommodate the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> simultaneous arrival of 24 facts into our expert system.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Assuming that all of our 2,000+ rules are completely isolated (i.e. no<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> rule i ever depends on any rule j, for all i,j) we want to consider<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> building (at start of day) a KSPool (size 24) , KBPool (size 24), and a<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> ThreadPoolExecutor (size 24, backed by BlockingQueue). As facts arrive<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> throughout the day, those that arrive simultaneously are Queue'd to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> the TPE, that then delegates the fact's need for service to a task<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Runnable, which in turn calls a KSPool[i].fireAllRules() (with<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> isolation to KBPool[i]). In such a scheme, we would potentially be<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> able to render decisions concurrently when facts arrive simultaneously ( capacity 24).<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Is this design ambition common w/in current DROOLs use cases? Does<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> the current (or future) DROOLS offering include any in-place<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> capability to Pool KS or Pool KB? If not, are there any potential DROOLs concerns or "gotchas"<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> wrt to our pursuing this ambition (in a "let's build this now!" prototype)?<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> As always, tremendous thanks to all in this community forum.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Ben D Cotton III<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Morgan Stanley & Co.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> OTC Derivatives Clearing Technology<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> 1221 AOTA Rockefeller Ctr - Flr 27<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> New York, NY 10020<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> (212)762.9094<<a href="tel:%28212%29762.9094" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">tel:%28212%29762.9094</span></a>><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="mailto:ben.cotton@ms.com%3cmailto:ben.cotton@ms.com" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">ben.cotton@ms.com<mailto:ben.cotton@ms.com</span></a>><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> ________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> NOTICE: Morgan Stanley is not acting as a municipal advisor and the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> opinions or views contained herein are not intended to be, and do not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> constitute, advice within the meaning of Section 975 of the Dodd-Frank<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Wall Street Reform and Consumer Protection Act. If you have received<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> this communication in error, please destroy all electronic and paper<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> copies and notify the sender immediately. Mistransmission is not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> intended to waive confidentiality or privilege. Morgan Stanley<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> reserves the right, to the extent permitted under applicable law, to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> monitor electronic communications. This message is subject to terms available at the following link:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="http://www.morganstanley.com/disclaimers" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">http://www.morganstanley.com/disclaimers</span></a><span class="Apple-converted-space"> </span>If you cannot access these<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> links, please notify us by reply message and we will send the contents<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> to you. By messaging with Morgan Stanley you consent to the foregoing.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> _______________________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> rules-users mailing list<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="mailto:rules-users@lists.jboss.org%3cmailto:rules-users@lists.jboss.org" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org</span></a>><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="https://lists.jboss.org/mailman/listinfo/rules-users" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">https://lists.jboss.org/mailman/listinfo/rules-users</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> ________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> NOTICE: Morgan Stanley is not acting as a municipal advisor and the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> opinions or views contained herein are not intended to be, and do not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> constitute, advice within the meaning of Section 975 of the Dodd-Frank<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Wall Street Reform and Consumer Protection Act. If you have received<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> this communication in error, please destroy all electronic and paper<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> copies and notify the sender immediately. Mistransmission is not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> intended to waive confidentiality or privilege. Morgan Stanley<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> reserves the right, to the extent permitted under applicable law, to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> monitor electronic communications. This message is subject to terms available at the following link:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="http://www.morganstanley.com/disclaimers" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">http://www.morganstanley.com/disclaimers</span></a><span class="Apple-converted-space"> </span>If you cannot access these<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> links, please notify us by reply message and we will send the contents<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> to you. By messaging with Morgan Stanley you consent to the foregoing.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> _______________________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> rules-users mailing list<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="mailto:rules-users@lists.jboss.org%3cmailto:rules-users@lists.jboss.org" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org</span></a>><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="https://lists.jboss.org/mailman/listinfo/rules-users" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">https://lists.jboss.org/mailman/listinfo/rules-users</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> ________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> NOTICE: Morgan Stanley is not acting as a municipal advisor and the<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> opinions or views contained herein are not intended to be, and do not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> constitute, advice within the meaning of Section 975 of the Dodd-Frank<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> Wall Street Reform and Consumer Protection Act. If you have received<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> this communication in error, please destroy all electronic and paper<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> copies and notify the sender immediately. Mistransmission is not<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> intended to waive confidentiality or privilege. Morgan Stanley<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> reserves the right, to the extent permitted under applicable law, to<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> monitor electronic communications. This message is subject to terms available at the following link:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><span class="Apple-converted-space"> </span><a href="http://www.morganstanley.com/disclaimers" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">http://www.morganstanley.com/disclaimers</span></a><span class="Apple-converted-space"> </span>If you cannot access these<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> links, please notify us by reply message and we will send the contents<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">> to you. By messaging with Morgan Stanley you consent to the foregoing.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">_______________________________________________<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; ">rules-users mailing list<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><a href="mailto:rules-users@lists.jboss.org" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">rules-users@lists.jboss.org</span></a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 14pt; font-family: 'Lucida Console'; "><a href="https://lists.jboss.org/mailman/listinfo/rules-users" style="color: purple; text-decoration: underline; "><span style="color: windowtext; text-decoration: none; ">https://lists.jboss.org/mailman/listinfo/rules-users</span></a><o:p></o:p></div></div><br><br><hr id="HR1"><br><span style="font-family: Arial; color: rgb(128, 128, 128); font-size: 7.5pt; ">NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link:<span class="Apple-converted-space"> </span><a href="http://www.morganstanley.com/disclaimers" style="color: rgb(128, 128, 128); text-decoration: underline; font-family: Arial; font-size: 7.5pt; ">http://www.morganstanley.com/disclaimers</a><span class="Apple-converted-space"> </span>If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.</span><br><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org" style="color: purple; text-decoration: underline; ">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users" style="color: purple; text-decoration: underline; ">https://lists.jboss.org/mailman/listinfo/rules-users</a></div></blockquote></div><br></body></html>