Open pzhang714 opened 3 years ago
We design Hyperscan as a performance oriented library so it requires comprehensive analysis at compile time to achieve best performance. This means that it may consume longer compile time and more memory for compiling purpose than other regex matching libraries. In general, we don't provide options for compile time tuning.
What's your test setup? How many patterns do you use and what do your patterns look like? It'll be helpful to know the hotspots at compile time for your patterns.
Supplement:
The parrtens in list 1 and list 2 above are all strings without regular expressions,For example, domain name;
When the parents in list 2 are all the same strings, a large amount of memory will be consumed in the compilation process.
First Question: When there are a large number of patterns, it takes a long time to compile. How can we speed up the compilation?
Second Question: When there are a large number of patterns, a lot of temporary memory is needed during hyperscan database compilation. Can I reduce the usage of temporary memory during compilation? If can, how to do it?