On 2014-02-06 17:17, John Hardin wrote:
On Thu, 6 Feb 2014, Kevin A. McGrail wrote:
I've discussed it with Alex a bit but one of my next ideas for the
Rules QA process is the following:
- we measure and report on metrics for the rules that are promoted
such as rank (existing), computational expense, time spent on rule.
I assume meta rules would combine the expense of their components?
Sounds interesting!
How about if one or more components were called more by more than one
meta-rule? It's perhaps not entirely fair to divide it evenly, since
that might imply that removing the metarule would kill off that CPU usage.
Perhaps documenting the cost of the individual components, summing them,
with a flag to indicate that some or all of the components are shared?
That sounds overly complex, but it at least gives the enterprising rule
author or server administrator the ability to understand what is happening.
--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren
