Benchmark

EDKTool supports a benchmarking mode. This allows a user to run multiple concurrent extraction sessions a number of times in order to test the performance of a grammar. The input document is read once and fed into each session. Timing information is produced once all runs have completed. Note that the input document must be plaintext; IDX files are not supported.

You can use wildcard expressions in the -e and -g parameters; see Wildcard Expressions in edktool for more information.

-l <licensefile>

The file containing a valid license key for Eduction.

If you do not specify a license key at the command line, edktool assumes that the location of the license file is licensekey.dat. If the license is kept in this location, you do not need to specify this parameter.

-i <inputfile>

The file to perform entity extraction on. The input file must be plaintext.

-c <configfile>

A configuration file controlling the extraction. The configuration file can be either an IDOL Server style .CFG configuration file or an XML configuration file. See Configuration Files for Eduction Settings.

You can specify one or more grammar files and one or more entities in place of a configuration file. Specifying a configuration file overrides the grammar or entity parameters.

-g <grammarfile>

A grammar file to use when -c is not used.

If you provide a grammar file but do not specify any entities with -e, Eduction extracts all entities in the grammar file.

Note that the MinScore parameter can only be used if you are using -c. This means that, although you can use a grammar that supports scoring as the value for -g, no matches will be filtered out based on that.

-e <entity>

The entities to extract when -c is not used. Separate multiple entities with a comma.

-d (Optional) Detail - causes the output to show the matching strings and indicate where they appear in the input.
-s <sessions> Number of sessions to run concurrently during each iteration of the benchmarking test.
-n <number> Number of iterations of the benchmarking test to run.
-b Set this parameter to read the input file in binary mode, rather than text mode. If you create a grammar file that only matches entities with Windows (CR LF) line endings and you run edktool on Windows, the input file must be read in binary mode for any matches to be found. Micro Focus recommends that you create grammar files capable of handling both Windows and Unix line endings.

The benchmarking option runs the specified number of concurrent sessions and iterations and then displays the timing for each run, with a summary showing the total number of observations, maximum and minimum times, and the standard deviation.


_FT_HTML5_bannerTitle.htm