Hi - Hyperscan lead architect here. Performance numbers will follow but we do need to be careful about sweeping claims. With the variety of regular expression w

Hi - Hyperscan lead architect here. Performance numbers will follow but we do need to be careful about sweeping claims. With the variety of regular expression workloads making a blanket claim about performance is like saying "my C compiler always produces code that's 25% faster than yours". That being said, we don't pay that much performance cost for generality relative to non streaming, single pattern engines in terms of performance. Mainly the cost is complexity of our solution and pattern support.