4 ms·

One of the Hyperscan developers commented on HN slightly over a year ago [1] that Intel had basically abandoned Hyperscan due to lack of sufficiently vocal cust

One of the Hyperscan developers commented on HN slightly over a year ago [1] that Intel had basically abandoned Hyperscan due to lack of sufficiently vocal customer interest. I hope that has changed, or is in the process of changing, because Hyperscan remains amazing. [1] https://news.ycombinator.com/item?id=27421665 https://news.ycombinator.com/item?id=27421665

jiggawatts 4y ago
Not enough three letter agencies in the US to fund big brother at scale? (One if the use cases of this library is scanning through bulk intercept data streams for a set of key words.)
- deleted 4y ago
  [deleted]
- Lammy 4y ago
  Best throw away all your CPUs then too: https://groups.google.com/g/comp.arch/c/UXEi7G6WHuU/m/Z2z7fC7Xhr8J https://groups.google.com/g/comp.arch/c/UXEi7G6WHuU/m/Z2z7fC... https://vaibhavsagar.com/blog/2019/09/08/popcount/ https://vaibhavsagar.com/blog/2019/09/08/popcount/ https://arxiv.org/abs/1611.07612 https://arxiv.org/abs/1611.07612
jandrese 4y ago
The official repo[1] is looking pretty dead. Edit: This is a surprisingly heavy build. Over 15 minutes on my somewhat older i5. I suggest using make -j instead of cmake -build to speed it up. Decent number of compiler warnings too. [1] https://github.com/intel/hyperscan https://github.com/intel/hyperscan
- Cu3PO42 4y ago
  In sufficiently new versions of cmake you can use cmake --build -j as well. It will be translated to whatever argument is required for the underlying build system to use parallel compilation, e.g. -j for make and -m for msbuild.
  - jandrese 4y ago
    It just seemed excessive for a regular expression library. For comparison the most recent version of PCRE built in almost exactly 26 seconds. Sadly the hyperscan build crapped out for me in the linking phase, failing to find a bunch of coreX and avx optimized memset functions.
KerrAvon 4y ago
That post and the ensuing discussion are somewhat depressing. I am curious as to how the team's progress was measured; did the team's manager not know they needed to solicit user testimonials? Someone had to be responsible for the existence of the team and their productivity. What was the disconnect?

jiggawatts 4y ago

Not enough three letter agencies in the US to fund big brother at scale? (One if the use cases of this library is scanning through bulk intercept data streams for a set of key words.)

deleted 4y ago
[deleted]
Lammy 4y ago
Best throw away all your CPUs then too: https://groups.google.com/g/comp.arch/c/UXEi7G6WHuU/m/Z2z7fC7Xhr8J https://groups.google.com/g/comp.arch/c/UXEi7G6WHuU/m/Z2z7fC... https://vaibhavsagar.com/blog/2019/09/08/popcount/ https://vaibhavsagar.com/blog/2019/09/08/popcount/ https://arxiv.org/abs/1611.07612 https://arxiv.org/abs/1611.07612

jandrese 4y ago

The official repo[1] is looking pretty dead. Edit: This is a surprisingly heavy build. Over 15 minutes on my somewhat older i5. I suggest using make -j instead of cmake -build to speed it up. Decent number of compiler warnings too. [1] https://github.com/intel/hyperscan https://github.com/intel/hyperscan

Cu3PO42 4y ago
In sufficiently new versions of cmake you can use cmake --build -j as well. It will be translated to whatever argument is required for the underlying build system to use parallel compilation, e.g. -j for make and -m for msbuild.
- jandrese 4y ago
  It just seemed excessive for a regular expression library. For comparison the most recent version of PCRE built in almost exactly 26 seconds. Sadly the hyperscan build crapped out for me in the linking phase, failing to find a bunch of coreX and avx optimized memset functions.

KerrAvon 4y ago

That post and the ensuing discussion are somewhat depressing. I am curious as to how the team's progress was measured; did the team's manager not know they needed to solicit user testimonials? Someone had to be responsible for the existence of the team and their productivity. What was the disconnect?