Regex Performance

Introduction

Regular expressions are commonly used in pattern search algorithms. This tool is based on the work of John Maddock (See his own regex comparison here) and the sljit project (See their regex comparison here).

Requirements

dependency	version
Cmake	>=3.0
Ragel	6.9
Python	>=3.0
Boost	>=1.57
Pcap	>=0.8
Autoconf	2.69 (*)
Automake	1.15 (*)
Autopoint	0.19.7 (*)
Gettext	0.19.7 (*)
Libtool	2.4.6 (*)
Git	2.11.0 (*)

(*) Tested with named version only. Older versions may work too.

Supported engines

The following regex engines are supported and covered by the tool:

The engines are built from their sources. In the case an installed engine should be used, the corresponding cmake variable INCLUDE_<name> has to be set to system. The configuration script tries to locate the library and uses the library for linking the benchmark. The same variable can be set to disabled to exclude an engine.

The configuration script distinguishes between nightly and other Rust toolchains to enable the SIMD-feature which is currently available in the nightly built only. The SIMD-feature improves the throughput of the regex crate for defined expressions.

Building the tool

The different engines have different requirements which are not described here. Please see the related project documentations.

In the case all depencies are fulfilled, just configure and build the cmake based project:

mkdir build && cd build
cmake ..
make

The make command will build all engines and the test tool regex_perf.

To build the test tool or a library only, call make with corresponding target, i.e.:

make regex_perf

Usage

The test tool calls each engine with a defined set of different regular expression on a given file. The repository contains a ~16Mbyte large text file (3200.txt) which can be used for measuring.

./src/regex_perf -f ./3200.txt

By default, the tool repeats each test 5 times and prints the best time of each test. The overall time to process each regular expression is measured and accounted. The scoring algorithhm distributes the fastest engine 5 points, the second fastest 4 points and so on. The score points help to limit the impact of a slow regular expression eninge test in comparision to the absolut time value.

You can specify a file to write the test results per expression and engine:

./src/regex_perf -f ./3200.txt -o ./results.csv