Follow up to my last post on Filter Nodes
In my last post I mentioned a new rule we added to our product to help with WMB/IIB/ACE performance by reducing the number of nodes.
So if you have a "Filter Node" you can look to combine the logic with any following "Compute Node" so that only one parsing of the message tree is required.
So we introduced a new rule for checking this in the flow logic:
R219 – Filter node following a Compute node is redundant (WMB)
To follow up on that, when working with WMB/IIB/ACE you would also be looking for the reverse. Where a "Filter Node" follows a "Compute Node".
Again, these two nodes can be combined into one to improve performance (less nodes, less tree parsing).
For this we have an existing rule:
R219 - Filter node following a Compute node is redundant (WMB)
Where the "Filer Node" logic can be replaced with a "RETURN FALSE" or multiple calls to "PROPAGATE TO".
If you are interested in finding out more about our product and these times don't suit, please drop me an email to:
Or contact me via the contact page on our website.
Regards
Richard