Thanks Mark, will try that.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Performance-monitoring-and-hotspot-detection-in-rules-tp1850756p1864068.html
Sent from the Drools - User mailing list archive at Nabble.com.
Mark,
Thanks for your reply. I figured 3 and 4 were currently possible but 1 and 2
puzzled me.
it interates from root to tip repeatedly, so you can't easily determine how
long it spends in each node
Sorry, looks like my prior statement (#2) was misleading. Actually, I don't
care so much about
On 07/11/2010 21:59, H.C. wrote:
Mark,
Thanks for your reply. I figured 3 and 4 were currently possible but 1 and 2
puzzled me.
it interates from root to tip repeatedly, so you can't easily determine how
long it spends in each node
Sorry, looks like my prior statement (#2) was misleading.
On 05/11/2010 20:52, H.C. wrote:
I am trying to implement a performance monitor to find the most problematic
rules in order to optimize performance. The main performance metrics I want
to gather are:
1. How any times a rule's conditions have been evaluated
2. How long each rule's condition
I am trying to implement a performance monitor to find the most problematic
rules in order to optimize performance. The main performance metrics I want
to gather are:
1. How any times a rule's conditions have been evaluated
2. How long each rule's condition evaluation took
3. How many times a
